-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Alexander E. Patrakov wrote: > [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) > [X] I deviate a lot from BLFS (not counting package updates as deviations)
The last two depend on what "a lot" means -- I generally add a bunch of configure options to packages in BLFS (for stuff that I find useful), but that's about it. > 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 > (X) User-based > ( ) RPM > ( ) 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: > [X] Knowing where each file comes from > [X] Clean uninstallation of a package > [ ] Removal of obsolete files when upgrading to a new version > [ ] Ability to upgrade toolchain components (most notably, glibc) painlessly > [ ] Ability to revert mistakes easily and quickly by installing an old > binary package > [ ] Ability to compile once, deploy on many macines > [X] Scripting the build I should note that "removal of obsolete files" (when I think about it) is done by removing everything before installing the new version. I should also note that while I do use the scripts, I don't think of them as critical. > 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 wen upgrading package versions > [X] Doesn't explain how to package software beyond BLFS > [ ] Requires learning another language/syntax besides bash shell syntax > [ ] Exists at all Of course, I reserve the right to ignore it if it exists at all, but I can't say that I definitely will. ;-) I also haven't looked into trying the DIY build either, but if I do that, then "interfer[ing] with config.site" will be a problem. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHy+sKS5vET1Wea5wRA7h8AKCFLhZwrhhf40uYNOzLPDKhPLo3BwCgjfOq eGfLotlKiRmKiPOas/X4zcU= =LGTs -----END PGP SIGNATURE----- -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
