I suspect that my submissions here will be much like those of a lot of 
other less-experienced users who don't subscribe to the dev-lists, but 
spreading the poll to other lists, like 'support', could get pretty 
chaotic...

> [ ] 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 *DONT* use LFS as my primary Linux system _YET_, precisely because i 
haven't implemented usable PM _YET_.

# The next 2 responses relate to my use of 'portage' on my day-to-day 
Gentoo-box...

> 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 # Portage, just because it's the native system

> 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
> [ ] 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 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
> 

Besides voicing my own individual eagerness for PM in LFS, i don't know 
how useful this will be, but am interested in finding out...

taipan
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to