Gentoo Archives: gentoo-dev

From: Tom Wijsman <TomWij@g.o>
To: gentoo-dev@l.g.o
Cc: hwoarang@g.o
Subject: Re: [gentoo-dev] Re: Banning modification of pkg-config files
Date: Fri, 09 May 2014 20:25:44
Message-Id: 20140509222527.2621c06e@gentoo.org
In Reply to: Re: [gentoo-dev] Re: Banning modification of pkg-config files by Markos Chandras
1 On Fri, 09 May 2014 21:10:50 +0100
2 Markos Chandras <hwoarang@g.o> wrote:
3
4 > On 05/09/2014 09:08 PM, Tom Wijsman wrote:
5 > > On Fri, 09 May 2014 20:57:29 +0100
6 > > Markos Chandras <hwoarang@g.o> wrote:
7 > >
8 > >> I was wondering, is there a good reason we keep our own pkgconfig
9 > >> files instead of communicating that to upstream and resolve that
10 > >> properly?
11 > >
12 > > Yes, when your "instead of ..." is not an option.
13 >
14 > Why not? If the package does not work out of the box then something is
15 > broken upstream?
16
17 Some upstreams don't care about Gentoo's practices like slotting and/or
18 dynamic linking; similarly, similar practices on other distributions.
19
20 > If it works for Debian but not for us then maybe we do something
21 > wrong?
22
23 This mixes two things. It currently works for the Lua maintainers, as
24 those pkgconfig files are present; just like they are present on Debian.
25
26 > >> What other distributions do? Or are we a special case and
27 > >> we need our own pc files?
28 > >
29 > > No, see https://bugs.gentoo.org/show_bug.cgi?id=509392#c23 which
30 > > reads:
31 > >
32 > > "You do realize that out of five distros (Fedora, Debian,
33 > > Slackware, SuSe, Mandriva) I checked five ship a .pc file?" by
34 > > mabi.
35 > >
36 >
37 > I am not talking about Lua here. It's a more general question.
38
39 Ah, I see; it's just that we come from the Lua context background, so
40 it'll often be used as example. As for in general, we'll indeed need to
41 investigate what other distributions do; but, Lua is that special case.
42
43 --
44 With kind regards,
45
46 Tom Wijsman (TomWij)
47 Gentoo Developer
48
49 E-mail address : TomWij@g.o
50 GPG Public Key : 6D34E57D
51 GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D

Attachments

File name MIME type
signature.asc application/pgp-signature