On 2016-12-24 Josh Triplett <j...@joshtriplett.org> wrote:
> On Sat, Dec 24, 2016 at 04:31:58PM +0100, Andreas Metzler wrote:
>> On 2016-12-24 Josh Triplett <j...@joshtriplett.org> wrote:
[...]
>>> While working on a way to automatically detect pkg-config dependencies,
>>> I noticed that autogen ships the pkg-config file autoopts.pc (for
>>> instance, /usr/lib/x86_64-linux-gnu/pkgconfig/autoopts.pc), which
>>> corresponds to the library in libopts25-dev. Please ship this
>>> pkg-config file in the libopts25-dev package, instead.
[...]
>> parts of the source code of binaries linking against libopts is usually
>> generated from template files by invoking autogen. Therefore source
>> packages usually b-d and require on autogen (not only libots25-dev) and
>> ./configure searches for autogen. autogen (the binary package) in turn
>> depends on libopts25-dev.
>> So imho shipping autoopts.pc in autogen is the right thing to do.
> I understand that packages may need both.
Hello,
Well, let me modify my original statement: libopts is _only_
used in conjuction with autogen. Packages therefore should never b-d
on libopts25-dev.
> However, the pkg-config file doesn't identify autogen; it identifies
> the libopts library, and provides the details needed to link against
> libopts. Having the pkg-config file in autogen diverges from every
> other library package that ships pkg-config files.
> It might also make sense to have a pkg-config file for autogen itself,
> which would live in the autogen package.
The pkg-config file provides info for the AutoOpts parser. It consists of
a) autogen which can be used to generate option parsing code from
template files ("pkg-config --variable=autogen autoopts"
and
b) libopts which is used by the generated code. ("pkg-config
--libs autoopts")
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
