On Sat, 1 Sep 2012 01:05:39 +0200 Michał Górny <[email protected]> wrote:
> On Fri, 31 Aug 2012 17:49:34 -0400 > Alexis Ballier <[email protected]> wrote: > > > On Fri, 31 Aug 2012 22:53:35 +0200 > > Michał Górny <[email protected]> wrote: > > > > [...] > > > I'm not sure if you're aware of it but Gentoo doesn't aim at > > > supporting solely Linux and no other system. > > > > elf != linux > > Gentoo != elf only. Prefix? Come on, some usecases do not make pkgconfig so vital for every gentoo install that it should be in @system. > > > Also, please tell me how to handle multiple slots sanely without > > > pkg-config in a package like Boost, for example. > > > > You should know since you are proposing a boost-utils.eclass :) > > Eh, the world would be so much better if boost provided pkg-config > files. > > For example, boost.m4 (provided by boost-m4) uses some wall-dumb > stubborn heuristics which always grabs newest boost and doesn't > provide any sane way to provide it with an older one... Yes, pkgconfig can be useful, sometimes... > > Anyway, my point was just to go from 'not providing a .pc is broken' > > to '.pc are useful and needed in some cases but not all' > > But these some cases where there are needed result in the necessity > of installing them, and making the build systems aware of them. I > don't see much point in adding a 'backwards compatibility' to it as > well. If the build system needs pkgconfig then the ebuild should depend on it, whats wrong with that ? I dont need pkgconfig to run the package after its built. For the same reason people have been working to _remove_ flex, m4, bison, autoconf, automake from @system, pkgconfig does not belong there either... > Ah, while we're at it. If a library has macros referring > to the functions of another library (or just types) in its public API, > it needs a pkg-config file. ELF dependencies are not enough, > and the gold linker will refuse to work because of a missing explicit > dependency. Eh, straight to the point where pkgconfig is not the solution to everything: a binary not using said macros but trusting pkgconfig will get overlinked. Documentation stating that when using these macros/functions one should link to the other lib would make things even better. A.
