> And why not? If some pieces were not required, then why did you build > them in the first place?
I only really consider package management important I will admit from the context of multi-part software suites...like KDE as one example. In that scenario, the entire system has QT as a dependency. Then there are some of the KDE components which don't have any other deps, so you can build them first after QT, and others which depend on those first pieces which only depend on QT. So yeah...to me strictly speaking, it's more about dependency management than package management as such; figuring out the build order for things, and which things need which other things. I don't think that can be automated completely, because it depends on the computer being able to gather its own information...which is one of the things that a human really needs to be doing. That's why RPM in particular can be such a mess...because it tries to do things that computers are known not to be very good at doing. Computers IMHO are only good at taking orders...they're most certainly NOT good at figuring out what orders to give themselves. The part that of course can be automated however, is the building of the individual pieces themselves. One thing I haven't seen in any system completely yet I don't think though (or certainly no system on Linux anywayz) is a system where dependencies and build order are worked out entirely manually, so that the computer doesn't have to do that...all it then has to do is get each piece and focus on building that as an individual object. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
