Re: [Helidelinux-devel] Dependency management for software packaging

[Hui Z. <zh...@wa...>]

On Wed, Mar 10, 2004 at 04:09:53PM +0000, Rolf Veen wrote:
> Dependency information is only meaningful for a combination of
> package/version/build-recipe. That means that probably a master
> file with a map 'package/version -> dependencies' is pretty useless.
> The correct map would be 'package/version/recipe -> dependencies'.
> Ugly.
> 
> That means that dependencies are more a property of the build
> recipe, a prerequisite for that particular recipe:
> 
> --
> pkg binutils-2.14
> 
> build
>   depends
>     bash, coreutils, diffutils, gcc, gettext,
>     glibc, grep, make, perl, sed, texinfo
>   recipe \
>     # here the build recipe
> 
> another_build
>   depends
>     # here other dependencies.
>   recipe \
>     # another recipe
> --
> 
> Rolf.
> --
> Just trying to think :-).

There is a lot repetition in the profile as for most recipies they
share a common set of dependency and even recipe itself. Currently my
approach is list the common build script (I even divided them into
unpack, config, build, install, postinstall to increase the
possibility to share ) and list recipe specific scripts in a
seperate entry with a prefix for that recipe. The installer is trained
to look in the common script if it couldn't find the recipe specific
script. I find it not only saves human energy to edit it, but also
increases the readability since it is obvious to spot each recipes
particular variance.

-Hui