Hello, I had actually been thinking about a couple of things of related note here.
First, could have a little more free-form wiki, free-form more being in what is added or included in the wiki. So if someone were to build openvpn say for example's sake, they could add an entry to the wiki on openvpn. Organize the entries by software, and version. Maybe with some general notes over the program as a whole. This would obviously be outside of the blfs page with no actual guarantees as to how said program would work on version x of LFS or if it will or will not work with specific versions, even how stable it may or may not be. But would be helpful to those building and resolving dependency of packages that don't have a page in blfs. Second. Maybe a script or small program that can take a tar file, and a requirements document and build a package to that. It's only other purpose would be to track what is currently installed on the system, for versioning and dependency tracking. The requirements file though could contain what is needed to build a package, but in a framework type of setup so that an individual can easily edit it to what is needed per their system configuration. This may be more out of the scope of blfs though, but would be a helpful tool. Any ways, just a couple of ideas, I don't know if the blfs book wiki can have other software builds or anything of the sort. Daniel -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
