On Thu, 29 Nov 2012 08:52:01 +0100 justin <j...@gentoo.org> wrote: > The only remaining problem is on the implementation side. As you can > imagine, this effort is nothing in which the upstreams are really > interested in. Therefore most of our .pc files are created inside the > ebuild. Eventually they will find their way back upstream, but currently > this is something gentoo specific, it's about choices. > > The eclass should just be a reduction of redundant code. And of course > its not meant to be a replacement to upstream work on packages with sane > buildsystems. Its just a last resort for corner cases like our > lapack/blas stuff, which do not have any reasonable option. > > I hope this clears my intention and makes it reasonable to have this eclass,
Nope, it doesn't. If the pkg-config file is created within an ebuild (or eclass), it is *completely unsuitable* to go anywhere. You should write a template, preferably 'mostly' compatible with the build system and put it into FILESDIR. Even if it's going to be redundant. This way, we have a simple, ready, clean, constant file which can be sent upstream or copied by any other distro. It also makes clear that the file is Gentoo-specific. -- Best regards, Michał Górny
signature.asc
Description: PGP signature
