I'm preparing a build-essential upload; build-essential currently
depends on dpkg-dev (>= 1.13.5). Should the dependency tightened? If
yes, which version should be used? If a version greater than 1.14.6 is
used, I have to depend on dpkg and dpkg-dev, because dpkg-dev only
requires dpkg (>= 1.14.6).

thanks, Matthias


--
To UNSUBSCRIBE, email to debian-dpkg-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Tue, 24 Jun 2008, Matthias Klose wrote:
> I'm preparing a build-essential upload; build-essential currently
> depends on dpkg-dev (>= 1.13.5). Should the dependency tightened? If
> yes, which version should be used?

Why do you want a versioned dependency in the first place?

I'm sorry, it seems that I don't get the point of your question.

Checking build-essential changelog's doesn't help me much either:
* Increased versioned dependency on dpkg-dev to 1.13.5 to provide
support for the OS and CPU variables.

> If a version greater than 1.14.6 is
> used, I have to depend on dpkg and dpkg-dev, because dpkg-dev only
> requires dpkg (>= 1.14.6).

Why would you need a specific version of dpkg?

Cheers,
--
Raphaël Hertzog

Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/


--
To UNSUBSCRIBE, email to debian-dpkg-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Raphael Hertzog writes:
> On Tue, 24 Jun 2008, Matthias Klose wrote:
> > I'm preparing a build-essential upload; build-essential currently
> > depends on dpkg-dev (>= 1.13.5). Should the dependency tightened? If
> > yes, which version should be used?
>
> Why do you want a versioned dependency in the first place?

because it depends on variable names found in
/usr/share/dpkg/archtable and introduced in 1.13.5.

> I'm sorry, it seems that I don't get the point of your question.
>
> Checking build-essential changelog's doesn't help me much either:
> * Increased versioned dependency on dpkg-dev to 1.13.5 to provide
> support for the OS and CPU variables.
>
> > If a version greater than 1.14.6 is
> > used, I have to depend on dpkg and dpkg-dev, because dpkg-dev only
> > requires dpkg (>= 1.14.6).
>
> Why would you need a specific version of dpkg?

I take this as answer that no specific version greater than 1.13.5 is
required.

thanks, Matthias


--
To UNSUBSCRIBE, email to debian-dpkg-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Tue, 24 Jun 2008, Matthias Klose wrote:
> > Why do you want a versioned dependency in the first place?
>
> because it depends on variable names found in
> /usr/share/dpkg/archtable and introduced in 1.13.5.

Ok.

> > Why would you need a specific version of dpkg?
>
> I take this as answer that no specific version greater than 1.13.5 is
> required.

Given that buildd run the latest (or at least a recent) version of the
package in the suite they're building for and that packages have to
build-depend on corresponding dpkg-dev versions when they make use of new
features, I don't see a reason to increase the dependency in
build-essential.

When we use new source formats by default, it might be a reason to ensure
that everybody has a dpkg recent enough to support the newer formats
but until then, I'd keep it as is.

If Guillem or anyone else see a reason to increase the dependency, they'll
speak up I guess.

Cheers,
--
Raphaël Hertzog

Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/


--
To UNSUBSCRIBE, email to debian-dpkg-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org