Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 05 Aug 2015 14:17:12 +0000
From:      bugzilla-noreply@freebsd.org
To:        gnome@FreeBSD.org
Subject:   [Bug 202006] textproc/libxml2: xml2-config --libs output lists private libraries causing overlinking
Message-ID:  <bug-202006-6497-y66MTdjdcy@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-202006-6497@https.bugs.freebsd.org/bugzilla/>
References:  <bug-202006-6497@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202006

--- Comment #4 from Kubilay Kocak <koobs@FreeBSD.org> ---
(In reply to Tijl Coosemans from comment #3)

I believe in this case, given the impact (incorrect linking / overlinking)
there is a net benefit to FreeBSD to fixing xml2-config, particularly with
regard to any other port that uses the same. The context here for the proposed
change is 'only support within the FreeBSD ports tree and packages'.

Additionally, while the patch does indeed 'adds a feature', it more precisely
corrects the default case, and adds an argument for any consumers that rely on
the prior behaviour to potentially use as a workaround. The expectation however
is that the existing output of xml2-config is always incorrect for --libs.

I agree (and use myself) the principle of staying as close to upstream. It is
however interesting to consider that the premise to always maintain incorrect
behaviours precludes ever fixing almost all classes of bugs in software.

I agree and believe the long term target/goal should be asterisk switching to
pkg-config, and I will report the issue upstream (and potentially add a patch
to the port), as well as xml2-config disappearing (or being fixed) upstream.

The attached patch to libxml2 at least gets us a step closer to the latter case
(xml2-config fixed), without impacting the the former (xml2-config disappears).

-- 
You are receiving this mail because:
You are on the CC list for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202006-6497-y66MTdjdcy>