Alexander E. Patrakov schrieb: > Jeremy Huntwork wrote: <snip> >> The main LFS module can be about the final system. Teaching users >> _concepts_ of the system, locations of key config files, useful shell >> tricks and tips, information about packages, examples of how to use the >> packages in a practical way, etc, etc. This should make LFS somewhat >> more accessible and easier for end users to pick and choose what it is >> they need out of it. > > +1 +1 from me, I don't want a new "distribution", there are enough out there, what I want is how to build my own system
>> To cover PM, we can create a very generic spec file for each package in >> such a way that an end user can either use it in their own custom >> scripts, run the commands manually, or with any number of PMs available. >> To that end, it may be necessary to maintain specific modules for the >> more advanced PMs with directions on how to employ the PM of your choice. all I expect from a "package manager" is what file belongs to which package or vice versa (that's why I use paco) >> To automate it all, again, when designing the system from the start, we >> make provision to snap-in whichever PM module a user has chosen. <snip> Regards Benjamin -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page