how will 'package-management' be implemented?

Kevin P. Fleming kpfleming at
Wed Apr 14 14:44:13 PDT 2004

Reinhard wrote:

> So with BLFS, I checked the dependencies and sorted the packages upon their 
> dependency-graph (build from the dependencies from the book).
> At package-ordering the level of the dependencies was also respected, means, 
> if the (end-)user choosed a package, wich is an optional dependency of 
> another package, the order will be changed to keep track of that.
> This means, that a different entry to the profiles has to be generated.

That's where I think we are differing; you are envisioning each user who 
wants to use a BLFS profile would use a tool to create their own 
customized profile from the BLFS book sources, where I am envisioning 
more of the current model where an already-built complete profile is 
downloaded and only the relevant parts are used (either manually or 

I can't say for sure which is better, but I can say that having to 
download the book sources and whatever XML-related tools are needed to 
produce a profile from those sources would be a significant hurdle for 
many people who just want to have a working profile. I'm not saying that 
having the _ability_ to do that isn't useful, because it certainly is, 
I'm just saying that IMHO the users who would want to work that way 
would be in the minority.

How would you propose an "automatically generated" profile would handle 
things like:

- configuration entities (LFS build location, downloaded package tarball 
location, etc.)

- package entities (tarball MD5/SHA-1 digests, etc.)

More information about the alfs-discuss mailing list