On 2/10/12 3:45 PM, Aleksej Saushev wrote:
Julio Merino<jmmv%julipedia.org@localhost> writes:On 2/10/12 12:20 PM, David Brownlee wrote:On 9 February 2012 20:43, Julio Merino<jmmv%julipedia.org@localhost> wrote:So again, what's the problem? glib is as much gnome as it is kde or irssi.I believe the issue is glib2 uses pkg-config to build, therefore updating pkg-config to a version which uses glib2 provides interesting opportunities for recursion...pkgsrc knows what the appropriate CFLAGS and LIBS values for every of the required libraries are based on the various BUILDLINK_* variables. You can easily feed those into configure to avoid the calls to pkg-config, and thus suppress the circular dependency.I don't quite understand why you want to put so high maintainance cost in one fourth of all packages
No-one has been able to explain yet why doing this upgrade increases the maintenance cost of the packages, much less one fourth of them.
just to make version number of one package grow. It is close to impossible to find any reason to justify such move.
Good luck maintaining obsolete sources. Or good luck rewriting this in C, but you'll soon realize that it's not as trivial as it seems. In any of these two cases, you will certainly be introducing a high maintenance cost.