Debian Bug report logs - #192008
dpkg-dev: dependencies from libtool and pkg-config files

Full log

🔗 View this message in rfc822 format

X-Loop: [email protected]
Subject: Bug#192008: dependencies from libtool and pkg-config files
Reply-To: Joey Hess <[email protected]>, [email protected]
Resent-From: Joey Hess <[email protected]>
Original-Sender: Joey Hess <[email protected]>
Resent-To: 
Resent-Date: Fri, 29 Aug 2003 05:18:05 UTC
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
X-Debian-PR-Message: report 192008
X-Debian-PR-Package: debhelper
X-Debian-PR-Keywords: 
Received: via spool by [email protected] id=Q192008.10621342397984
          (code Q ref 192008); Fri, 29 Aug 2003 05:18:05 UTC
Received: (at 192008-quiet) by bugs.debian.org; 29 Aug 2003 05:17:19 +0000
Received: from murphy.debian.org [146.82.138.6] 
	by master.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 19sVjF-0007Qi-00; Thu, 28 Aug 2003 17:58:57 -0500
Received: from kitenet.net (kitenet.net [64.62.161.42])
	by murphy.debian.org (Postfix) with ESMTP id 55CC320198
	for <[email protected]>; Thu, 28 Aug 2003 17:58:52 -0500 (CDT)
Received: from dragon.kitenet.net (pm3naxs21-45.access.naxs.com [216.98.95.45])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(Client CN "Joey Hess", Issuer "Joey Hess" (verified OK))
	by kitenet.net (Postfix) with ESMTP
	id 63B1517FEB; Thu, 28 Aug 2003 22:58:49 +0000 (GMT)
Received: from joey by dragon.kitenet.net with local (Exim 3.35 #1 (Debian))
	id 19sUEI-00010I-00; Thu, 28 Aug 2003 17:22:54 -0400
Date: Thu, 28 Aug 2003 17:22:33 -0400
From: Joey Hess <[email protected]>
To: Michel Dänzer <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
References: <[email protected]> <[email protected]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="lEGEL1/lMxI0MVQ2"
Content-Disposition: inline
In-Reply-To: <[email protected]>
User-Agent: Mutt/1.5.4i
Sender: Joey Hess <[email protected]>
Delivered-To: [email protected]
X-Spam-Status: No, hits=-20.8 required=4.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE_2,
	      QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES,
	      USER_AGENT_MUTT
	autolearn=ham version=2.53-bugs.debian.org_2003_8_27
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_8_27 (1.174.2.15-2003-03-30-exp)

[Message part 1 (text/plain, inline)]

Michel Dänzer wrote:
> > Assuming all this is done (and it sounds like something that would
> > belong in dpkg to me, as well as requiring modificatons of lots of -dev
> > packages to provide the shlibs file equivilants), then you still 
> > have to get all the packages to use the new debhelper utility and 
> > modify their control files.
> 
> There's no need to convert all packages right away; getting these
> dependencies right may well be easy for the majority of packages,
> nevertheless the others seem to have caused considerable porting
> headaches recently (that's the impression I got; I'll gladly be proved
> wrong). The idea is that those packages which cause problems in this
> area could use the new tool as they are discovered, instead of adding
> more kludges which are bound to break again sooner or later.
> 
> > I think you would be better served by adding something to lintian to try
> > to detect missing -dev dependnecies, and filing some bug reports. Unlike
> > shared library dependnencies, -dev dependencies rarely change, and when
> > they do, the package maintainer always has reason to know about it (they
> > have to change the build dependnecies too).
> 
> But the main point of my proposal is exactly that packages should only
> have to build-depend on packages they use directly, not also on other
> packages those happen to depend on.

That's already common practice.

> Similarly, if I want to write a program that uses say libpisock, I want
> to just install libpisock-dev, I don't care that it needs
> libreadline4-dev as well. And neither should the libpisock-dev
> maintainer have to.

I disagree; if the libpisock-dev maintainer does not know what other
development packages are used by his package, he needs to find out.
Especially since this set will be quite similar to what his package must
build-depend on. I'm not sure if that was intended as a concrete
example, but note that libpisock-dev in fact depends on libncurses-dev.

-- 
see shy jo

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.