Apologies for jumping into this thread when you are seemingly a good way along to "resolving" the PM issue but the question/idea I have is somewhat PM related.
If you are going to hive off the files produced for each package into a tarball for later deployment, how easy would it be to create package-specific ownerships for the to-be-installed files, along the lines of one strand of package management that has appeared on here at times - the "username-per-package" approach. I've always appreciated that the username-per-package PM method was probably a little too "intense" for the general audience building from scratch, however it strikes me that now you have a clearly defined "payload", altering the ownership of each one to match that PM method might have some benefits. I always found that the underlying issues it highlighted eg, files needing to go somewhere not originally with permission to do so or what files sometimes clash between the packages to be part of the learning process. I guess the issue wopuld be that the end-user (end-installer?) would still have to be told how to resolve the clashes but then LFS often directs users to use this package's version of a flle of that one's explicitly anyway. Apologies for the noise, if it is seen as such, Kevin -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
