Alexander E. Patrakov wrote: > Please reply to this message (please, limit this to the lfs-dev list > only) and mark with "X" the items that apply. If the answer is not the > same on your different Linux systems, write numbers of systems to > which each answer applies instead of a simple "X" mark. The resuts may > or may not be used for determining the future course of LFS. They will > certainly be used to verify or disprove my guess about the way the LFS > community is now split.
I'm continuing with the ~ for sometimes. For my dev system (or systems at times), I follow the book religiously except for the bootscripts. > > [X] I am an editor of LFS or one of the related projects > [X] I use LFS as my primary Linux system > [X] I use LFS on more than one PC (including virtual machines) > [~] I deviate a lot from LFS (not counting package updates as deviations) > [~] I deviate a lot from BLFS (not counting package updates as deviations) > > I use the following package management technique: > ( ) It's all in my head! > ( ) I trust the lists of files in the book > ( ) I rebuild everything every three months or less, so there is no > need to manage anything! > ( ) Installation script tracing with installwatch or checkinstall > ( ) Installation script tracing with some other tool > ( ) Timestamp-based "find" operation > ( ) User-based > ( ) RPM > ( ) DPKG > ( ) Simple binary tarballs produced with DESTDIR > ( ) Other DESTDIR-based method of producing binary packages > (X) Other It's really a timestamp-based setup for now, but in the works is a spec file of sorts (bash variables) to account for modified files and backups/diffs of them. > > I use the following features provided by a package manager: > [X] Knowing where each file comes from > [X] Clean uninstallation of a package > [X] Removal of obsolete files when upgrading to a new version > [ ] Ability to upgrade toolchain components (most notably, glibc) painlessly > [X] Ability to revert mistakes easily and quickly by installing an old > binary package This one should be reworded: Ability to revert mistakes easily and quickly by reverting modified files to their pre-installation state and removing the rest of the installed files. :-) > [ ] Ability to compile once, deploy on many macines > [X] Scripting the build Though I don't use my PM for that yet, following on heels of the recent PM threads, I have began adding the needed bits to my existing tool, to create what I've decided to call lspec files, which will easily allow for an automated build. As usual for me, plain, ordinary, easy bash. > > I will ignore the future LFS advice on package management if it > [ ] Can't be applied on a busy machine where many files are > accessed/modified everyy minute > [ ] Can't be used to transfer packages to another machine > [ ] Interferes with config.site files described in DIY-linux > [X] Will clobber configuration files when upgrading package versions > [ ] Doesn't explain how to package software beyond BLFS > [ ] Requires learning another language/syntax besides bash shell syntax > [ ] Exists at all > -- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
