Re: Bug#349318: libxft-dev: please do not export unnecessary libraries in xft.pc
On Sun, 2006-01-22 at 14:36 -0500, David Nusinow wrote: The mesa NMU will go in shortly, and after that I need to figure out exactly how to handle the transition to FHS compliance. I'm not entirely sure I'm happy with how Daniel did it (although I've yet to look at it closely). I'm going to do a full analysis and post an RFC either on debian-x or debian-devel about it. Please at least CC -x, as I don't (have time to) read -devel. -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Bug#349318: libxft-dev: please do not export unnecessary libraries in xft.pc
Package: libxft-dev
Version: 2.1.7-1
Severity: important
Tags: upstream
Hi folks,
So, I suppose most of you have read
http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html about
problems with packages depending on libraries that they don't use,
particularly as relates to a potential libfreetype transition. One library
that currently exposes freetype (and other libs) in its pkg-config .pc file,
but shouldn't, is libxft.
Please consider (and forward upstream) the attached patch which moves all of
the library dependencies of libxft into the Libs.private variable in xft.pc,
so that they aren't used on Debian except for static linking. I have not
touched the 'Requires' field; even though packages which link to libXft
should not need to link to libfontconfig, the pkg-config 'Requires' field
controls both CPPFLAGS and LDFLAGS, and Xft includes fontconfig headers --
unfortunately the pkg-config maintainer has not been convinced that CPPFLAGS
from Requires.private should be propagated, despite the fact that there are
many examples of this scenario in Debian... (this is bug #340904, for those
who care.)
FWIW, since September 2003 FreeType has supported pkg-config; however, I
wouldn't recommend that Xft use pkg-config dependencies for libfreetype
unless this Requires.private CPPFLAGS issue is resolved. :/
Oh, also, there seems to be a pre-existing bug in this .pc file, in that
-lX11 is specified for static linking, but -L/usr/X11R6/lib is not...
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
diff -u xft-2.1.7/debian/changelog xft-2.1.7/debian/changelog
--- xft-2.1.7/debian/changelog
+++ xft-2.1.7/debian/changelog
@@ -1,3 +1,11 @@
+xft (2.1.7-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix xft.pc to not export freetype and xrender as part of the interface
+used for shared linking; expose them only in Libs.private instead.
+
+ -- Steve Langasek [EMAIL PROTECTED] Sun, 22 Jan 2006 02:32:25 -0800
+
xft (2.1.7-1) unstable; urgency=low
* New upstream release.
only in patch2:
unchanged:
--- xft-2.1.7.orig/xft.pc.in
+++ xft-2.1.7/xft.pc.in
@@ -11,5 +11,6 @@
Description: X FreeType library
Version: @VERSION@
Requires: fontconfig
-Libs: -L${libdir} -lXft -lX11 ${freetypelibs} ${xrenderlibs}
+Libs: -L${libdir} -lXft
+Libs.private: -lX11 ${freetypelibs} ${xrenderlibs}
Cflags: -I${includedir} ${freetypecflags} ${xrendercflags}
signature.asc
Description: Digital signature
Bug#349318: libxft-dev: please do not export unnecessary libraries in xft.pc
tags 349318 + fixed-upstream On Sun, Jan 22, 2006 at 02:44:28AM -0800, Steve Langasek wrote: So, I suppose most of you have read http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html about problems with packages depending on libraries that they don't use, particularly as relates to a potential libfreetype transition. One library that currently exposes freetype (and other libs) in its pkg-config .pc file, but shouldn't, is libxft. Please consider (and forward upstream) the attached patch which moves all of the library dependencies of libxft into the Libs.private variable in xft.pc, so that they aren't used on Debian except for static linking. I have not touched the 'Requires' field; even though packages which link to libXft should not need to link to libfontconfig, the pkg-config 'Requires' field controls both CPPFLAGS and LDFLAGS, and Xft includes fontconfig headers -- unfortunately the pkg-config maintainer has not been convinced that CPPFLAGS from Requires.private should be propagated, despite the fact that there are many examples of this scenario in Debian... (this is bug #340904, for those who care.) FWIW, since September 2003 FreeType has supported pkg-config; however, I wouldn't recommend that Xft use pkg-config dependencies for libfreetype unless this Requires.private CPPFLAGS issue is resolved. :/ Oh, also, there seems to be a pre-existing bug in this .pc file, in that -lX11 is specified for static linking, but -L/usr/X11R6/lib is not... This has already been fixed in the modular tree (/cvs/xorg/lib, as opposed to /cvs/xlibs). But I guess the CPPFLAGS scenario remains. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#349318: libxft-dev: please do not export unnecessary libraries in xft.pc
Processing commands for [EMAIL PROTECTED]: tags 349318 + fixed-upstream Bug#349318: libxft-dev: please do not export unnecessary libraries in xft.pc Tags were: upstream Tags added: fixed-upstream On Sun, Jan 22, 2006 at 02:44:28AM -0800, Steve Langasek wrote: Unknown command or malformed arguments to command. So, I suppose most of you have read Unknown command or malformed arguments to command. http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html about Unknown command or malformed arguments to command. problems with packages depending on libraries that they don't use, Unknown command or malformed arguments to command. particularly as relates to a potential libfreetype transition. One library Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349318: libxft-dev: please do not export unnecessary libraries in xft.pc
On Sun, Jan 22, 2006 at 10:57:12AM +, Daniel Stone wrote: tags 349318 + fixed-upstream On Sun, Jan 22, 2006 at 02:44:28AM -0800, Steve Langasek wrote: So, I suppose most of you have read http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html about problems with packages depending on libraries that they don't use, particularly as relates to a potential libfreetype transition. One library that currently exposes freetype (and other libs) in its pkg-config .pc file, but shouldn't, is libxft. Please consider (and forward upstream) the attached patch which moves all of the library dependencies of libxft into the Libs.private variable in xft.pc, so that they aren't used on Debian except for static linking. I have not touched the 'Requires' field; even though packages which link to libXft should not need to link to libfontconfig, the pkg-config 'Requires' field controls both CPPFLAGS and LDFLAGS, and Xft includes fontconfig headers -- unfortunately the pkg-config maintainer has not been convinced that CPPFLAGS from Requires.private should be propagated, despite the fact that there are many examples of this scenario in Debian... (this is bug #340904, for those who care.) FWIW, since September 2003 FreeType has supported pkg-config; however, I wouldn't recommend that Xft use pkg-config dependencies for libfreetype unless this Requires.private CPPFLAGS issue is resolved. :/ Oh, also, there seems to be a pre-existing bug in this .pc file, in that -lX11 is specified for static linking, but -L/usr/X11R6/lib is not... This has already been fixed in the modular tree (/cvs/xorg/lib, as opposed to /cvs/xlibs). But I guess the CPPFLAGS scenario remains. Excellent. I don't suppose there's any ETA for this fix making it to unstable? I've found at least one package that could benefit from it, and I imagine there are plenty more. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#349318: libxft-dev: please do not export unnecessary libraries in xft.pc
On Sun, Jan 22, 2006 at 04:18:21AM -0800, Steve Langasek wrote: On Sun, Jan 22, 2006 at 10:57:12AM +, Daniel Stone wrote: tags 349318 + fixed-upstream On Sun, Jan 22, 2006 at 02:44:28AM -0800, Steve Langasek wrote: So, I suppose most of you have read http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html about problems with packages depending on libraries that they don't use, particularly as relates to a potential libfreetype transition. One library that currently exposes freetype (and other libs) in its pkg-config .pc file, but shouldn't, is libxft. Please consider (and forward upstream) the attached patch which moves all of the library dependencies of libxft into the Libs.private variable in xft.pc, so that they aren't used on Debian except for static linking. I have not touched the 'Requires' field; even though packages which link to libXft should not need to link to libfontconfig, the pkg-config 'Requires' field controls both CPPFLAGS and LDFLAGS, and Xft includes fontconfig headers -- unfortunately the pkg-config maintainer has not been convinced that CPPFLAGS from Requires.private should be propagated, despite the fact that there are many examples of this scenario in Debian... (this is bug #340904, for those who care.) FWIW, since September 2003 FreeType has supported pkg-config; however, I wouldn't recommend that Xft use pkg-config dependencies for libfreetype unless this Requires.private CPPFLAGS issue is resolved. :/ Oh, also, there seems to be a pre-existing bug in this .pc file, in that -lX11 is specified for static linking, but -L/usr/X11R6/lib is not... This has already been fixed in the modular tree (/cvs/xorg/lib, as opposed to /cvs/xlibs). But I guess the CPPFLAGS scenario remains. Excellent. I don't suppose there's any ETA for this fix making it to unstable? I've found at least one package that could benefit from it, and I imagine there are plenty more. I'm working on it. The mesa NMU will go in shortly, and after that I need to figure out exactly how to handle the transition to FHS compliance. I'm not entirely sure I'm happy with how Daniel did it (although I've yet to look at it closely). I'm going to do a full analysis and post an RFC either on debian-x or debian-devel about it. Once that's figured out, the libs, drivers, and server can all go in to experimental, as they're finished right now. Following that, there's some work to be done on bundling the apps and packaging a few miscellaneous things that shouldn't take too long. If it all works, I'm going to throw it to unstable and see how it goes. I can't give you a real time line for this, since it's been mainly me doing this on the Debian side so far, but I'm hoping to get all of modular in to unstable within the next two or three months, but it's possible that it'll go faster. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349318: libxft-dev: please do not export unnecessary libraries in xft.pc
On Sun, Jan 22, 2006 at 02:36:58PM -0500, David Nusinow wrote: On Sun, Jan 22, 2006 at 04:18:21AM -0800, Steve Langasek wrote: On Sun, Jan 22, 2006 at 10:57:12AM +, Daniel Stone wrote: This has already been fixed in the modular tree (/cvs/xorg/lib, as opposed to /cvs/xlibs). But I guess the CPPFLAGS scenario remains. Excellent. I don't suppose there's any ETA for this fix making it to unstable? I've found at least one package that could benefit from it, and I imagine there are plenty more. I'm working on it. The mesa NMU will go in shortly, and after that I need to figure out exactly how to handle the transition to FHS compliance. I'm not entirely sure I'm happy with how Daniel did it (although I've yet to look at it closely). I'm going to do a full analysis and post an RFC either on debian-x or debian-devel about it. Once that's figured out, the libs, drivers, and server can all go in to experimental, as they're finished right now. Following that, there's some work to be done on bundling the apps and packaging a few miscellaneous things that shouldn't take too long. If it all works, I'm going to throw it to unstable and see how it goes. But libxft2 is already split out and installed in /usr/lib, so it should be just a simple matter of packaging the new upstream version in order to fix this particular one? Would an NMU be welcome here, or could some other member of the XSF pick it up? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#349318: libxft-dev: please do not export unnecessary libraries in xft.pc
On Sun, Jan 22, 2006 at 03:05:48PM -0800, Steve Langasek wrote: But libxft2 is already split out and installed in /usr/lib, so it should be just a simple matter of packaging the new upstream version in order to fix this particular one? Would an NMU be welcome here, or could some other member of the XSF pick it up? Argh, I'd forgotten that this is one of the few that aren't built from xorg-x11. Ok, I'll grab the latest and upload it ASAP. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
