[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    [gentoo-dev] Re: Banning modification of pkg-config files (was: [gentoo-project] Re: Call For Agenda
From:       Matti Bickel <mabi () gentoo ! org>
Date:       2014-05-09 18:21:21
Message-ID: 536D1CA1.8060903 () gentoo ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 05/09/2014 04:07 PM, hasufell wrote:
> I ask the council to vote on banning pkg-config files that would
> be added or renamed downstream (at least this will prevent new
> violations).

I want to repeat my stance from the linked bug that making this a
policy or calling on council to add more weight to existing devmanual
bits is adding red tape that from my point of view decreases the
quality of Gentoo. Asking me to remove the pkg-config file for lua-5.2
or removing the modifications to 5.1 will kill support for packages
depending on these files existing.

As long as there's stuff expecting the file to be around, I have a
hard time committing a "fix" that will increase the breakage in the tree.

Let me be clear: once packagers of lua using apps tell me they no
longer need the .pc file for their stuff to work, I'll remove it
promptly or switch to the reduced version you get from calling "make
pc" for lua-5.2.

However, all the linked bugs and commits seem to address the point
that debian *renames* the lua .pc files. You seam to take particular
issue with slotting lua (which requires us to rename them as well).

I'm on the record saying that I don't like this solution. However,
I've made it clear (and the eselect-lua module implements this) that
there's always a lua.pc, liblua.so, etc of the user's chosing. It's
also the only thing we got to resolve the stalemate of lua users
lagging behind releases. If you have better ideas, please let me know.

Since this is a technical matter, please direct further discussion to
the gentoo-dev ML.

Cheers, Matti
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQJ8BAEBCgBmBQJTbRyhXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNzE1M0M4QzQxMzM4REREMjMzQjg4NUZE
REY5NzFGMTE4RUVBNUU2AAoJEN35cfEY7qXmEGsP/39WprTJ9T4FmBiNO+xnPDS5
H3FbNmdN/YjyOy5OSBMbS2j9fxQXEJ5AdAeE5gWyEiNEji0wmecWqP2FNAEtoZ5c
H4IJ92eSyw99zz424GU2eS0uNCkujn/xOIxWHmrvWiCiUYzF150KHl9nrRRdRrwB
dKjyz7nXiEyZDS1dQ4gyTMeA6mUIrr0bFl0G8Kfy0dPWB0elpe837no/S/fRcKtM
syb9+QL3TvYlCVbONkcFxtOQyij+9OTcMffITVysiHjy5+CNKoVjw3zKUPoYQN1f
CSdob9x/W+vUrZt1gjEbxukqyBMlBokapvN1nwwi7T6IczHCPpDtnvN6TncX/0VW
AkwB5wAgtxjsf6bu8vvx6D6gRYDoYFgXHe81m+SHfmbkDaIAUk67QdN3WHg4R0o7
fgJ5KVx5KowemNdM3SybJlTTOkt6ROaqkzMRsXDC+vDwQEZ4881zLpttGFfEJPjR
tfej+FrhoMv5yir8joUIePwXLXluF1D0DO8RlrUpGTAFkwY1QqdA0ho3rwRpDZDT
70iWKepz6Xgj7mKlVjSF6C5iPxyKYMbgVgH+4IK4MCWYvam/tLwtbuegDmF/txUM
5P4a4fQUzvmGFmDOkRsnJBj5Gnez8J5DxzB3hmRJgT+TVKxlfRCQ4Ajh31VHQXun
nw5cxcrYETn9jQtdmbqJ
=JnYK
-----END PGP SIGNATURE-----

[prev in list] [next in list] [prev in thread] [next in thread]