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

[Rolf V. <rol...@he...>]

One file that has dependency information is the ./configure
script that many packages have. But not all have it and the
information is 'not easily' (:-)) extracted.

On the other hand, once dependency info is generated for
a package/version, it is stable. That is, once generated, it
can be published on a website and used by others. Maybe
an automated system that is later hand-tuned can be a
compromise solution. Once the first system is build and we
have its (tuned) dependency file published on helidelinux.sf.net
for example, subsequent builds do not need to create that file
again.

But:

- how do we handle optional deps
- what are the basic units: packages, files.

Rolf.