lrn1986 at gmail.com
Fri Mar 30 23:10:27 PDT 2012
-----BEGIN PGP SIGNED MESSAGE-----
On 31.03.2012 9:34, Paul Bender wrote:
> On 3/30/2012 9:49 PM, Tollef Fog Heen wrote:
>> ]] Paul Bender
>>> Making pkg-config dependent on anything will ensure that
>>> pkg-config is dropped over time. The inane idea that it is ok
>>> to make pkg-config depend on a package that uses pkg-config is
>>> sure to guarantee that distributions will not update
>>> pkg-config. I maintain a Linux distribution and I have no plans
>>> to upgrade pkg-config because of the the inane decision to
>>> create this dependency. Because of this decision, I expect that
>>> within five years pkg-config will no longer exist. Nobody
>>> maintaining a distribution wants this circular dependency.
>>> Therefore, we will end up dropping pkg-config.
>> Such a circular dependency is quite common in lower parts of the
>> toolchain, so people bootstrapping distributions have to deal
>> with this anyway. For people not maintaining toolchains, it's
>> not a problem.
> It is not "quite common". I maintain a toolchain, so I know. The
> only circular dependency is between gcc and glibc. Based on your
> statement you must not maintain a toolchain.
In 2011 Debian Squeeze had 2231 loops in build-dependencies of its
packages. This number is probably somewhat lower by now though.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the pkg-config