It's first-come first-served. In principle a newer-yet lib_version could go back to the default locations, provided that the original pango1-xft2-dev was totally expurgated--the -shlibs could stay around for compatibility.
However, this brings up something I've been curious about. Since a fair number of packages are set up such that things that build against them look for a common root directory under which there are include/ and lib/ (pilot-link10 is an example I'm familiar with), I'm curious why we don't also allow for a simpler directory tree in such cases, e.g. a %p%N with %p%N/include and %p%N/lib . That way each libversion can just go in its own %N subdirectory of %p . On Monday 28 January 2008 10:47:29 pm [EMAIL PROTECTED] wrote: > Thanks very much for answering those questions. It is a bit ironic I guess > that in the pangocairo branch the pangocairo library gets hidden. I'm > certainly no expert, but as long as everthing is getting upgraded in one > cohort, wouldn't this be a good time to give the newer package the default > locations? > > On Sun, 27 Jan 2008 13:37:56 -0500 > "Alexander K. Hansen" <[EMAIL PROTECTED]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > William Scott wrote: > | Hi folks: > | > | A package I am maintaing, coot, in its latest development phase > | (which I try to participate in), requires gtk+2 v. 2.10 or higher, > | which therefore requires the fink "pangocairo" branch, which in turn > | continues to mystify me (despite having read the fink wiki "The > | Great Gnome Update" page > > > http://wiki.finkproject.org/index.php/Fink:Packaging:The_Great_Gnome_Update > > | ). > | > | > | > | I have a few very basic questions: > | > | 1. Is there an estimated date of release, or goal for one? > > "soon" > > | 2. What is the story with fink package pango1-xft2-ft219-dev and > | pango1-xft2-dev ? Why does only the first one provide > | libpangocairo, and if the two conflict and replace one another, why > | does the first one hide stuff in /sw/lib/pango-ft219/lib ? > > They're development packages for two vintages of pango1. In > accordance with our shared library policy, the development packages should > conflict, and the libraries have to be able to coexist, so > pango1-xft2-ft219-shlibs installs its libraries in > /sw/lib/pango-ft219/lib. The -dev package probably installs there so > that there's a common root directory for the headers and the > libraries. > > | 3. I've used PKG_CONFIG_PATH=/sw/lib/pango-ft219/lib/pkgconfig:$ > | {PKG_CONFIG_PATH} to get coot's configure to find pangocairo.pc, > | which it then does. Later in the compilation, libtool tries to find > | all the associated libtool files (libpangocairo-1.0.la, > | libpango-1.0.la and so forth) in /sw/lib and fails. Similarly, it > | starts looking for pangocairo.pc and pango.pc in /sw/lib and fails. > | I made symbolic links as a work-around, but obviously that isn't a > | viable solution. So my questions are: > | > | a) Is pango1-xft2-ft219-dev obsolete and/or depreciated in favor of > | pango1-xft2-dev ? If so, what should I tell the author of coot to > | do about this? Which one should we be aiming to use a year from now? > > It's the other way around. The "ft219" means that it uses > "freetype219", which corresponds to newer versions of freetype2. > > | b) How do I force libtool to do the right thing? > | > | > | For what it is worth, coot has about 150 dependencies, which apart > | from the above, all seem to work well enough to enable it to > | compile. > | > | Thanks. > | > | Bill Scott > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHnM+BB8UpO3rKjQ8RAvniAJwM0OMmBDnYnClombZmiWBTfNnZmACfQzDz > a+lz85+PpKd1QBsWFqdZY4k= > =gCDT > -----END PGP SIGNATURE----- > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Fink-devel mailing list > Fink-devel@lists.sourceforge.net > http://news.gmane.org/gmane.os.apple.fink.devel -- Alexander K. Hansen akh AT finkproject DOT org Fink User Liaison and Documenter ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
