"Cory R. Crooks" wrote: > IMHO the hardest part about this is the "front end" to the README. We > want something so that newbie's DON'T have to read text files to install > something. We want them to be able to select a few options (or have > those options selected for them), and then hit the "Install" button and > not worry. If it were feasible to parse some abitrary file (README or > not) and extract compile time options, installation directories > (specially for pre-built binaries w/ wierd install paths like "Put xyz > where libsomething.so.1 is, but don't put abc their, put abc in where > libsomethinelse.so.1.0 is, and symlink it to ... you get my drift), and > other useful info, it wouldn't be all that hard to implement the rest... Well the installer could read a "distribution"-file that holds systemwide information of where to usually store the files. This would allow to deal with distrib-dependent setups. ciao BoP -- Boris Povazay -- Send posts to: kde@lists.netcentral.net Send all commands to: kde-request@lists.netcentral.net Put your command in the SUBJECT of the message: "subscribe", "unsubscribe", "set digest on", or "set digest off" PLEASE READ THE ARCHIVED MESSAGES AT http://lists.kde.org/ BEFORE POSTING ********************************************************************** This list is from your pals at NetCentral