Post-LFS Package management

Yann Kerhervé kerherve at
Thu Jun 29 09:30:27 PDT 2000

On Thu, Jun 29, 2000 at 10:01:50AM -0400, Daniel P. Clery wrote:
> Just wondering what thoughts anyone has regarding keeping track of what belongs to what software package after the base system is installed and up and running. This has always been one of my frustrations with Slackware, but dpkg and rpm seem to involved and tied into Redhat's and Debian's design philosophy. I'm looking at stow, and am wondering what else is out there to keep track of what's installed, what versions, and to facilitate upgrading the same. Something that I can go from the source and make a package would be really nice. Any suggestions would be appreciated.

I've tried stow... the idea behind is fairly simple. Stow is quite ok
for me ... BUT there are problems with symlinks. I use LFS 2.3.2 and
/usr/etc is a link to /etc and so on. It's difficult to deal with that
(well, it's my experience) with stow.

> As an aside, I'm loving this project and think it's a great thing, if only as a tool to learn WHY the other distributions are the way they are. I like the idea of being able to take what I want and leave the rest.
Mail archive:
IRC access: server: port: 6667 channel: #LFS
Unsubscribe: email lfs-discuss-request at and put
"unsubscribe" (without the quotation marks) in the body of the message
(no subject is required)

More information about the lfs-dev mailing list