I could have expanded on those two areas a bit more. What I specifically meant by free-form, was that software packages could be added to the wiki easily and consistently. And have it organized by software then by version of the software so that even if a specific build was needed than it could be built that way. So that it would work on whichever version of lfs system was being used.. maybe even a built on lfs version, either way.
The dependency tracking for the program would just be a hey you need this and this software installed first before you can build this package or the build will fail. Maybe even a these are optional dependencies, and have fun. Maybe a slightly better way is to just house the requirement files, the requirement files could download the tar file as well. I would be more than happy to template out a wiki and start getting things together for that, it wouldn't be an overnight type of thing but I could probably piece together a few things. I was actually planning on building myself an internal site that would also have a wiki for such things just so I could keep track of various items including software builds, because when I have to rebuild a system I don't want to have to track down all the instructions I used to build packages that are outside of LFS/BLFS. The success rate though for such a project really does include on how many other people would actually be interested in having either a little more open wiki, and or the installer. Daniel -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
