Managing required packages in nALFS

Jamie Bennett jamie_bennett at
Fri Sep 13 06:40:08 PDT 2002

> -----Original Message-----
> From: Vassili Dzuba [mailto:vassilidzuba at]
> AFAIK, ALFS (if there is such a beast) does not provide any 
> mean to check the required
> packages when building a new one. While it is not very 
> important when building a LFS,
> which is a rather sequential process, it is more so when 
> building BLFS packages
> as we are more likely in that case to build only some of 
> them, and in a random order.
> After having been bitten a few times, i patched nALFS to :
> - create a stamp file after a package has been build successfully
> - provide a <check> element that allows to check if a given 
> stamp file exists,
>   and interrupt the process if it does not
> - provide a <stamp> element to build a stamp file outside of 
> a package,
>   if needed.
> An example of use of <check>  is :
>     <package name="librep" version="&librep-version;">
>         <check>gmp</check>
>         <check>gdbm</check>

  Just been thinking about this one as I'm half way through one of
my own patches. What happens if for example gmp has its own
dependencies? nALFS could complain that librep needs gmp but
ideally it should complain that it needs gmp _and_ whatever
gmp depends on.

  This would require recursively traversing profiles which opens
up a whole new can of worms :( I'm trying to have a go at this one
but its not as easy as I first thought (or maybe I can't see the
easy way of doing it).

>Vassili Dzuba

-- --------------------------------------
- Jamie Bennett     - 18 St Peters Terrace - jamie at -
- Software Engineer - Lower Bristol Road   -                   -
- PCP Microproducts - Bath, England        -                   -
Unsubscribe: send email to listar at
and put 'unsubscribe alfs-discuss' in the subject header of the message

More information about the alfs-discuss mailing list