Poll about package management

[USM Bish]

> On Mon, 03 Mar2008 "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 am an editor of LFS or one of the related projects
> [*] I use LFS as my primary Linux system
> [*] 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
> ( ) Other
>  
> I use the following features provided by a package manager:
> [*] Knowing where each file comes from (and goes to)
> [*] 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 packag
> [ ] Ability to compile once, deploy on many machines
> [ ] Scripting the build
> 
> 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 every minute
> [ ] Can't be used to transfer packages to another machine
> [ ] Interferes with config.site files described in DIY-linux
> [*] 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
>

An LFS user (with nil contribution so far)

Bish