[pkg-ggz-maintainers] About versioned build dependencies

[Josef Spillner]

Alle 22:43, martedì, 15. agosto 2006, Peter Eisentraut ha scritto:
> Most GGZ packages have versioned build dependencies like
>
> libggz-dev (>= 0.0.12)
>
> I'm not sure if this is necessary.

Right now they're needed in most cases, at least for 0.0.14 again. There are 
too many function additions which are then used by the upper layers.
They're backward compatible (I hope), so we don't need to bump the major 
library version number, but not forward compatible.

> My concern is that if we set these  
> too tightly, then uploading a new upstream version will take forever,
> because you need to wait a couple of days between each step in the
> dependency chain.

Why doesn't the autobuilder figure this out automatically? If I upload 
packages A, B and C, and those depend on each other in some way always 
requiring the latest version, it should build them in this order.
Since the order of compiling GGZ packages hasn't changed in ages, providing 
an "order" hints file to the build daemon should be possible, to create 
clusters of packages which are only processed all at once or not at all.

> Then again, if the implementation is such that these 
> are needed, we should probably upgrade them and perhaps set them using
> an automatic dpkg substitution variable.

I would have to read more docs about this first. If you mean the 
${Source-Version} entries, then they always make sense for the relationship 
of a library package to its -dev package, but I'm not sure we should use them 
across libraries.

Josef

-- 
The GGZ Gaming Zone - http://www.ggzgamingzone.org/