The Pangocairo Has Landed

Thanks to the hard work of countless developers and testers, the
"pangocairo" branch has now been merged back into the main distro for
fink's "unstable" trees for 10.4 (and 10.5). The glib/gtk/gnome core
libraries are up to the GNOME2.20 and most libraries and major
packages build and work for at least one person.

Thanks also to our users for their patience during this upgrade. Let
us know about any problems you have, so that we can get them fixed. I
suspect given that on the order of 500 package suites were upgraded,
there may be a shake-down period. Also, it may take a while for the
various mirrors to catch up, so please try several (including the
originals, not just the master-mirror pool) if you are having trouble
downloadingq a source.

Dependencies have been set so that things should upgrade in the
correct order automatically. Note that once you have begun to upgrade
a machine, some packages may become broken until those packages are
upgraded (an unfortunate situation that was unavoidable due to the
upstream pango and gtk changes).

As best I can tell, all bug-fixes that were applied to the public
packages during the pangocairo testing phase were merged into the
updated pangocairo packages, but I assume some could have gotten
lost. Check cvs diffs if something that was fixed is suddenly
re-broken...sorry in advance if so!

Technical notes:

All of unstable is coherently using the pango1-xft2-ft219 library
instead of pango1-xft2; only -ft219 should be used for anything in
unstable. You will probably need to use PKG_CONFIG_PATH and/or -L and
-I flags to make it visible. Likewise, you will need similar
mechanisms to make some other modern support libraries visible
(pango1's freetype219 dependency, fontconfig2, etc.). There are many
examples of the various approaches in the existing packages. Packages
in the submissions queue will likely need some attention.

In fink CVS dists/10.4/unstable, the "pangocairo-pre-merge" tag points
to the trunk just prior to pangocairo-branch being merged back into
the trunk and "pangocairo-post-merge" points to the trunk just after
the merge.

The contents of the head of pangocairo-branch are identical to
pangocairo-post-merge. Users who were testing the pangocairo cvs
branch on an active fink can switch back to HEAD with no dependency
disasters or loss of sanity. Users who stay in the branch will be
greeted with a warning that they are using an EOL'ed branch when they
selfupdate. You can recognize this situation by the availability but
subsequent build failure of a "fink" package whose revision ends in a
"2" (32 or 42) instead of the usual "1", which is only present in this
EOL'ed banch.

Finch, the machine that hosts the PDB website and some other
infrastructure services is not feeling well, so it may take a while
for all our mirrors and web-pages to sync all the data and files.

dan

--

-- 
Daniel Macks
dmacks <at> netspace.org
http://www.netspace.org/~dmacks

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/