On Jan 14, 2004, at 6:31 PM, Martin Costabel wrote:
The real fix would be to lean on the freetype2 guys to make them fix the upstream sources. Why for god's sake did they have to put a "freetype" directory inside include/freetype2? This header file should be named <freetype2/freetype.h>.
Hi Martin,
Why do you always pick on those guys. What they did is completely standard , eg 2 examples of today :
/sw/var/logs# locate pygtk.h /sw/include/pygtk-2.0/pygtk/pygtk.h /sw/include/pygtk/pygtk.h /sw/var/logs# locate gtkhtml.h /sw/include/gtkhtml-1.1/gtkhtml/gtkhtml.h /sw/include/gtkhtml-2.0/libgtkhtml/gtkhtml.h /sw/include/gtkhtml/gtkhtml.h /sw/include/libgtkhtml-3.0/gtkhtml/gtkhtml.h
And the reasons for doing so are obvious.
It is only because fink chooses not to install things in the normal places
/usr or /usr/local (and hence need to set explicit flags -L%p/lib or -I%p/include)
that we have difficulties with this : it seems more like a
fink problem than a problem of those packages.
(cf recent msg of pogma on ways to solve this at the fink level by having
fink editing the .la , .pc, and -config files at the end of an install)
Best,
Jean-Francois
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
