I wrote: (recording my own vote)
> [X] I am an editor of LFS or one of the related projects > [ ] 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) > [X] 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 > (1) 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 > (1) RPM (just an experiment) > ( ) DPKG > ( ) Simple binary tarballs produced with DESTDIR > ( ) Other DESTDIR-based method of producing binary packages > ( ) Other > > I use the following features provided by a package manager: > [ ] 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 > [ ] Ability to compile once, deploy on many machines > [X] Scripting the build > > I will ignore the future LFS advice on package management if it > [X] Can't be applied on a busy machine where many files are > accessed/modified every minute > [X] Can't be used to transfer packages to another machine > [X] Interferes with config.site files described in DIY-linux > [X] Will clobber configuration files wen upgrading package versions > [ ] Doesn't explain how to package software beyond BLFS > [ ] Requires learning another language/syntax besides bash shell syntax > [ ] Exists at all -- Alexander E. Patrakov -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
