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

Package: lintian; Maintainer for lintian is Debian Lintian Maintainers <[email protected]>; Source for lintian is src:lintian (PTS, buildd, popcon).

Reported by: "Michel Dänzer" <[email protected]>

Date: Mon, 5 May 2003 14:18:07 UTC

Severity: wishlist

Reply or subscribe to this bug.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to [email protected], Dpkg Development <[email protected]>, [email protected]:
Bug#192008; Package dpkg-dev. (full text, mbox, link).


Acknowledgement sent to "Michel D�nzer" <[email protected]>:
New Bug report received and forwarded. Copy sent to Dpkg Development <[email protected]>, [email protected]. (full text, mbox, link).


Message #5 received at [email protected] (full text, mbox, reply):

From: "Michel Dänzer" <[email protected]>
To: Debian Bug Tracking System <[email protected]>
Subject: dpkg-dev: dependencies from libtool and pkg-config files
Date: Mon, 05 May 2003 16:06:48 +0200
Package: dpkg-dev
Version: 1.10.10
Severity: wishlist

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


As the number of packages using libtool and pkg-config increases, a problem
related to them seems to become more common: library -dev packages often
lack dependencies on the -dev packages of libraries they need to link
correctly. As a consequence, packages which build depend on them need to
artificially build depend on those as well, or they fail to autobuild.

I think a tool which generates these dependencies from .la and .pc files
(and others I forget?) would be very valuable.

This bug might be more appropriate for debhelper, but I thought I'd submit
it here for a start. Feel free to reassign.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+tm/7WoGvjmrbsgARAiDrAJ9byhdEfw+3kUttUAKYA9ryNFQe1QCglIZd
Hcsx2RuiFOdSbkz89ObJC2A=
=+k6O
-----END PGP SIGNATURE-----



Information forwarded to [email protected], Dpkg Development <[email protected]>, [email protected]:
Bug#192008; Package dpkg-dev. (full text, mbox, link).


Acknowledgement sent to Wichert Akkerman <[email protected]>:
Extra info received and forwarded to list. Copy sent to Dpkg Development <[email protected]>, [email protected]. (full text, mbox, link).


Message #10 received at [email protected] (full text, mbox, reply):

From: Wichert Akkerman <[email protected]>
To: [email protected], [email protected]
Cc: [email protected]
Subject: Re: Bug#192008: dpkg-dev: dependencies from libtool and pkg-config files
Date: Mon, 5 May 2003 23:00:04 +0200
reassign 192008 debhelper
thanks

Previously Michel D?nzer wrote:
> I think a tool which generates these dependencies from .la and .pc files
> (and others I forget?) would be very valuable.

I feel this indeed belongs in a package like debhelper.

Wichert.

-- 
Wichert Akkerman <[email protected]>      It is simple to make things.
http://www.wiggy.net/                     It is hard to make things simple.




Bug reassigned from package `dpkg-dev' to `debhelper'. Request was from Wichert Akkerman <[email protected]> to [email protected]. (full text, mbox, link).


Information forwarded to [email protected]:
Bug#192008; Package debhelper. (full text, mbox, link).


Acknowledgement sent to Joey Hess <[email protected]>:
Extra info received and forwarded to list. (full text, mbox, link).


Message #17 received at [email protected] (full text, mbox, reply):

From: Joey Hess <[email protected]>
To: [email protected], Michel Daenzer <[email protected]>
Subject: Re: dependencies from libtool and pkg-config files
Date: Thu, 21 Aug 2003 16:33:56 -0400
[Message part 1 (text/plain, inline)]
I don't feel that parsing .la files will be useful. Not all packages use
libtool. Anyway, there is nothing of value in those files that cannot be
found in other ways.

It might be possible to run objdump on the library to get the libraries
a library links to, use heuristics to find the corresponding .so files,
and from there dpkg -S to get -dev package names. But then you need to
deal with cases like multiple -dev packages that can both serve for a
library. You have to deal with special cases like libc6-dev, which the
above mechanism would always add to the dependnency list, and whch
should not be included. Sounds a lot like the shlibs files mechanism and
dpkg-shlibdeps, doesn't it?

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.

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). This does not strike me as a
place where automation is desirable.

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

Information stored:
Bug#192008; Package debhelper. (full text, mbox, link).


Acknowledgement sent to Michel Dänzer <[email protected]>:
Extra info received and filed, but not forwarded. (full text, mbox, link).


Message #22 received at [email protected] (full text, mbox, reply):

From: Michel Dänzer <[email protected]>
To: Joey Hess <[email protected]>
Cc: [email protected]
Subject: Re: dependencies from libtool and pkg-config files
Date: 23 Aug 2003 19:01:15 +0200
On Thu, 2003-08-21 at 22:33, Joey Hess wrote: 
> I don't feel that parsing .la files will be useful. Not all packages use
> libtool. Anyway, there is nothing of value in those files that cannot be
> found in other ways.

Absolutely, I was probably too focussed on libtool because the problems
I saw were related to it.

> It might be possible to run objdump on the library to get the libraries
> a library links to, use heuristics to find the corresponding .so files,
> and from there dpkg -S to get -dev package names. But then you need to
> deal with cases like multiple -dev packages that can both serve for a
> library. You have to deal with special cases like libc6-dev, which the 
> above mechanism would always add to the dependnency list, and whch should 
> not be included. 

Anything covered by build-essential could be excluded?

> Sounds a lot like the shlibs files mechanism and dpkg-shlibdeps, 
> doesn't it?

Indeed, it's similar.

> 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.

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.


-- 
Earthling Michel Dänzer   \  Debian (powerpc), XFree86 and DRI developer
Software libre enthusiast  \     http://svcs.affero.net/rm.php?r=daenzer



Information stored:
Bug#192008; Package debhelper. (full text, mbox, link).


Acknowledgement sent to Joey Hess <[email protected]>:
Extra info received and filed, but not forwarded. (full text, mbox, link).


Message #27 received at [email protected] (full text, mbox, reply):

From: Joey Hess <[email protected]>
To: Michel Dänzer <[email protected]>
Cc: [email protected]
Subject: Re: dependencies from libtool and pkg-config files
Date: Thu, 28 Aug 2003 17:22:33 -0400
[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)]

Information stored:
Bug#192008; Package debhelper. (full text, mbox, link).


Acknowledgement sent to Michel Dänzer <[email protected]>:
Extra info received and filed, but not forwarded. (full text, mbox, link).


Message #32 received at [email protected] (full text, mbox, reply):

From: Michel Dänzer <[email protected]>
To: Joey Hess <[email protected]>
Cc: [email protected]
Subject: Re: dependencies from libtool and pkg-config files
Date: Fri, 29 Aug 2003 20:20:53 +0200
On Thu, 2003-08-28 at 23:22, Joey Hess wrote:
> Michel Dänzer wrote:
> > 
> > > 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.

It's always been supposed to be that way, sure, unfortunately reality
looks quite different sometimes.


> > 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.

He'll see it in the generated dependencies. :)

> 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.

But where's the dependency on libreadline4-dev? This little example I
dug up quickly may be flawed, but I've seen many more while tracking
down autobuild failures on powerpc.


BTW, as you correctly observed that this would be very similar to what
dpkg-shlibdeps does, maybe it could be extended with this functionality
relatively easily? I took a quick look at it, but that reminded me why I
don't like some aspects of perl. :\


-- 
Earthling Michel Dänzer   \  Debian (powerpc), XFree86 and DRI developer
Software libre enthusiast  \     http://svcs.affero.net/rm.php?r=daenzer



Information forwarded to [email protected], Joey Hess <[email protected]>:
Bug#192008; Package debhelper. (full text, mbox, link).


Acknowledgement sent to Michel Dänzer <[email protected]>:
Extra info received and forwarded to list. Copy sent to Joey Hess <[email protected]>. (full text, mbox, link).


Message #37 received at [email protected] (full text, mbox, reply):

From: Michel Dänzer <[email protected]>
To: [email protected]
Subject: Proof of concept
Date: Fri, 28 May 2004 16:29:27 +0200
[Message part 1 (text/plain, inline)]
Here's a proof of concept script which determines development
dependencies from header, libtool and pkgconfig files. Do you think this
is worth exploring further?


-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Libre software enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer
[dh_devdeps (application/x-perl, attachment)]

Information forwarded to [email protected], Debhelper Maintainers <[email protected]>:
Bug#192008; Package debhelper. (Sun, 25 May 2014 21:36:04 GMT) (full text, mbox, link).


Acknowledgement sent to <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debhelper Maintainers <[email protected]>. (Sun, 25 May 2014 21:36:04 GMT) (full text, mbox, link).


Message #42 received at [email protected] (full text, mbox, reply):

From: "VMH GmbH" <[email protected]>
To: "192008" <[email protected]>
Subject: Nachfolgend finden Sie Freie Stellen vom 23.05.2014
Date: Thu, 3 Jan 2002 06:42:03 GMT
Sehr geehrte/r Arbeitsuchender,

folgendes Arbeitsangebot ist für alle geeignet, da diese Arbeit ohne Vorwissen auch von zu Hause zu bewerkstelligen ist. Der Arbeitnehmer hat keine Ausgaben und muss keine besonderen Kenntnisse mitbringen. Die benötigte technische Ausrüstung wird von uns frei zur Verfügung gestellt. Zu Ihren Aufgaben gehört die Vorbereitung der Dokumentenbearbeitung, die Koordinierung, das Erstellen von Mediatheken, das Erstellen von Ebooks und die Betreuung von Onlinebibliotheken. Wir bieten eine attraktive Bezahlung in Höhe von 18€ pro Stunde. 

Unser Unternehmen verfügt über internationale Firmensitze in ganz Europa und wir arbeiten im Onlinebereich. Derzeit sind wir auf der Suche nach neuen Mitarbeitern. 

Worauf wir bei unseren Mitarbeiter Wert legen wäre: Sie verfügen über ein Paar Stunden Zeit am Tag, sie verfügen über ein Paar Stunden Zeit am Tag, Sie besitzen Flexibilität, Sie arbeiten gern von zu Hause, Sie besitzen eine teamorientierte Arbeitsweise und Grundkenntnisse von MS-Office sind von Vorteil. 

Konnten wir Ihr Interesse wecken? Dann freuen wir uns über Ihre Bewerbung! Senden Sie Ihre vollständigen Bewerbungsbögen an: [email protected]
Wir freuen uns auf Ihre Bewerbung.

Mit freundlichen Grüßen

VMH GmbH




Information forwarded to [email protected], Debhelper Maintainers <[email protected]>:
Bug#192008; Package debhelper. (Sun, 08 Feb 2015 14:06:05 GMT) (full text, mbox, link).


Acknowledgement sent to <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debhelper Maintainers <[email protected]>. (Sun, 08 Feb 2015 14:06:05 GMT) (full text, mbox, link).


Message #47 received at [email protected] (full text, mbox, reply):

From: "Busch SC" <[email protected]>
To: "192008" <[email protected]>
Subject: Agentur für Arbeit bietet neue Arbeitsstellen
Date: ---, 8 Feb 2015 14:02:08 GMT
Lieber Bewerber,

unser Kunde ist ein erfolgreiches, europaweit agierendes Unternehmen und sucht gerade neue Angestellte zur Stärkung des Teams im europäischen Raum. 

Die Leistungen werden Eu weit gefragt, und Sie haben die Möglichkeit unabhängig von Ihrem Wohnort einzusteigen. Wir bieten Aufträge für jeden. Die Arbeitsstelle kann sowohl von Rentnern, Hausfrauen als auch nebenberuflich aufgenommen werden. 
Verpackungsaushilfe, Sekretärservice, Begutachter, und vieles mehr wird derzeit angeboten. 

Es werden Ihnen aktuelle Aufträge und die entsprechende Bezahlung angeboten und Sie treffen die Auswahl. Jede Aufgabe wird unterschiedlich vergütet, normalerweise verdienen Sie bei 3-5 Stunden am Tag 1400 bis 1900 Euro Brutto im Monat. 
Sie haben keinerlei Ausgaben und können sofort bei uns einsteigen. 

Kennziffer ZP-783-36 Es sind 14 offene Jobs zu besetzen. 

Die nötige technische Ausrüstung wird von uns ohne weitere Kosten zur Verfügung gestellt. Die Beschäftigung kann gerne von Rentnern, Hausfrauen und auch nebenberuflich ausgeführt werden. 
Worauf wir bei unseren Mitarbeiter Wert legen wären Gewissenhaftigkeit, Pünktlichkeit und Diskretion, Ehrlichkeit, Zielstrebigkeit, Flexibilität, Freundlichkeit
Haben Sie Interesse weitere Informationen zu erhalten? Wir bieten Ihnen herausfordernde Aufgaben, interessante Perspektiven und attraktive Konditionen. Bitte bewerben Sie sich per Email mit Ihren vollständigen Bewerbungsunterlagen, Ihres frühestmöglichen Eintrittstermins sowie der Kennziffer. [email protected] Sie erhalten weitere Unterlagen zugeschickt. 


Wir freuen uns auf Ihre Bewerbung.

Mit freundlichen Grüßen

Busch SC
Rue d’Alger 40
Orly 3354




Information forwarded to [email protected], Debhelper Maintainers <[email protected]>:
Bug#192008; Package debhelper. (Sun, 14 Jun 2015 02:51:03 GMT) (full text, mbox, link).


Acknowledgement sent to <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debhelper Maintainers <[email protected]>. (Sun, 14 Jun 2015 02:51:03 GMT) (full text, mbox, link).


Message #52 received at [email protected] (full text, mbox, reply):

From: "Becker AG" <[email protected]>
To: "192008" <[email protected]>
Subject: Arbeitsvorschlag für 2015
Date: ---, 14 Jun 2015 02:33:10 GMT
Sehr geehrte/r 192008,

Vermittlungsagentur stellt Ihnen nachfolgend eine attraktive Arbeitsstelle in einem kompetenten Team von zu Hause aus vor, ohne Fahrzeit, ohne Anfahrt, ohne Verkehrsstress. Wir haben qualifizierte und effektive Arbeitsplätze nicht nur in der Stadt, sondern auch auf dem Land europaweit und bieten dabei hervorragende Qualität für unsere Auftraggeber. 
Ab sofort suchen wir:
Mitarbeiter (m/w) für Home-office Tätigkeit in der Abteilung Telekommunikation und Büroarbeit 

Wir bieten Ihnen einen Arbeitsplatz in Festanstellung oder als Gewerbetreibender mit einem Stundenlohn von 20 € pro Stunde in eigenverantwortlichen Arbeitsweise und einer familienfreunflichen Beschäftigungsform, sowie eine abwechslungsreiche Tätigkeit ohne Arbeitsweg mit flexiblen Arbeitszeiten. 
Es werden keine Fachkenntnisse vorausgesetzt. Die Einarbeitung findet schrittweise durch kompetente Kollegen statt. Die benötigte technische Ausstattung stellen wir Ihnen ohne weitere Kosten zur Verfügung. Die Arbeitsstelle kann sogar nebenberuflich ausgeführt werden, sowie von Rentnern und Hausfrauen. 

Ihre Anforderungen:

- Unproblematischer Umgang mit Email, PC und Internet
- Deutsch fließend, Fremdsprachen wären von Vorteil
- Genauigkeit und Zielstrebigkeit

Ihre Aufgaben sind:

- Unterlagen empfangen, überarbeiten und weitersenden
- Dokumente scannen/kopieren
- Emails bearbeiten
- Tätigkeit im Home Office in freier Zeiteinteilung
- Arbeit mit zur Verfügung gestellten Büroausstattungen

Sie sind bereit für flexible Tätigkeit und die Arbeit im Home-office? Wenn wir Ihr Interesse geweckt haben, senden Sie uns Ihre Bewerbung per E-Mail an: [email protected] 
Wir freuen uns auf Ihre Bewerbung, Ihre persönlichen Unterlagen behandeln wir selbstverständlich vertraulich. 

Es grüßt Sie Ihre

Becker AG




Information forwarded to [email protected], Debhelper Maintainers <[email protected]>:
Bug#192008; Package debhelper. (Thu, 08 Oct 2015 21:33:04 GMT) (full text, mbox, link).


Acknowledgement sent to Bertrand Marc <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debhelper Maintainers <[email protected]>. (Thu, 08 Oct 2015 21:33:04 GMT) (full text, mbox, link).


Message #57 received at [email protected] (full text, mbox, reply):

From: Bertrand Marc <[email protected]>
To: [email protected]
Subject: dependencies from libtool and pkg-config files
Date: Thu, 08 Oct 2015 23:30:16 +0200
[Message part 1 (text/plain, inline)]
Hello,

I have to say I was a bit surprised not to find a way to generate
dependencies from pkg-config files.

Is this still (11 years later) unfit for debhelper ? If not, I think it
would make a very good lintian check. What do you think ? Should we
reassign this bug to lintian ?

Cheers,
Bertrand



[signature.asc (application/pgp-signature, attachment)]

Information forwarded to [email protected], Debhelper Maintainers <[email protected]>:
Bug#192008; Package debhelper. (Fri, 23 Oct 2015 15:09:03 GMT) (full text, mbox, link).


Acknowledgement sent to Bertrand Marc <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debhelper Maintainers <[email protected]>. (Fri, 23 Oct 2015 15:09:03 GMT) (full text, mbox, link).


Message #62 received at [email protected] (full text, mbox, reply):

From: Bertrand Marc <[email protected]>
To: [email protected], [email protected]
Subject: dependencies from libtool and pkg-config files
Date: Fri, 23 Oct 2015 17:07:22 +0200
[Message part 1 (text/plain, inline)]
reassign 192008 lintian
thanks

Dear lintian developpers,

I think the script written by Michel Dänzer in 2004 (!) would make a
pretty good lintian check for -dev packages.

Would you consider integrate this into lintian ?

Regards,
Bertrand

[signature.asc (application/pgp-signature, attachment)]

Bug reassigned from package 'debhelper' to 'lintian'. Request was from Bertrand Marc <[email protected]> to [email protected]. (Fri, 23 Oct 2015 15:09:14 GMT) (full text, mbox, link).


Information forwarded to [email protected], Debian Lintian Maintainers <[email protected]>:
Bug#192008; Package lintian. (Sat, 04 Feb 2017 05:18:02 GMT) (full text, mbox, link).


Acknowledgement sent to [email protected]:
Extra info received and forwarded to list. Copy sent to Debian Lintian Maintainers <[email protected]>. (Sat, 04 Feb 2017 05:18:02 GMT) (full text, mbox, link).


Send a report that this bug log contains spam.


Debian bug tracking system administrator <[email protected]>. Last modified: Tue May 13 08:19:11 2025; Machine Name: bembo

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU General Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.