Here are my responses. I use a homegrown pkg manager. It used to be
based on the pkg-user + fakeroot approach, but the latest one I am
using has the pkg-user stuff removed since I found it was adding a lot
of complexity without much benefit. My current PM uses a fakeroot
approach by building and fakeroot installation as a non-root user and
then untarring the created install tarball with some preInstall and
postInstall scripts.

>From the PM techniques mentioned at
<http://www.linuxfromscratch.org/lfs/view/development/chapter06/pkgmgt.html>,
I have in the past used Timestamp Based, Tracing Installation Scripts,
& User Based Management.

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

NOTE: Currently my primary system is Ubuntu but will soon be replaced with LFS.

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
(X) 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
[X] Removal of obsolete files when upgrading to a new version
[X] 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
[~] 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
[ ] Doesn't explain how to package software beyond BLFS
[X] Requires learning another language/syntax besides bash shell syntax
[ ] Exists at all

-- 
Tushar Teredesai
   mailto:[EMAIL PROTECTED]
   http://www.linuxfromscratch.org/~tushar/
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to