[lfs-dev] Once more: Package Management

Jeremy Huntwork jhuntwork at lightcubesolutions.com
Sat May 19 12:43:41 PDT 2012

On 5/19/12 1:15 PM, DJ Lucas wrote:
> My hope is that build order is still a manual process where the user
> determines build order herself. Dependency checking is done only at
> build time and that optional deps remain optional. If there will be
> automation, how do we determine what optional deps to pull in?

Sorry, I meant to answer this question better in the last reply.

I think I would aim to keep the BLFS book as close as it is today in 
terms of allowing a someone to 'choose your own path'. Where that gets 
interesting is how to fit that into a new workflow with shared binary 
packages. From what I can see, there's three options:

1. Make the policy to not build the official binaries with _any_ of the 
optional dependencies present.

2. Make the policy for to the dev to build with _all_ of the optional 
dependencies listed present.

3. Choose some 'sane' set of defaults to build against, but mark that 
certain ones are not strictly required.

This also gets into the realm of the difference between run-time and 
build-time dependencies, as well as the reasons for splitting some 
packages into sub packages - but I'll leave those for perhaps a little 
later when this topic has gotten a bit more circulation. :)


More information about the lfs-dev mailing list