Le 24 févr. 2006 à 06:26, Daniel Johnson a écrit :
It's me again.
And no I'm not looking to take over Gnome. :-)
Anyway, the brand new libgnomeprint2.2-2.12.1-1001 package requires
a BuildDepends on bison. It fails to build with the system's
version. I assume the same is also true in the other trees.
What's the correct procedure for these things? If a package has a
real maintainer I'll email them, obviously. But for a package like
this, should I just go ahead and make the change? What's the best
way to be useful? Aside from assuming the role of fink-gnome-core
of course. ;-)
From my experience with gnome:
1 - libgnomeprintui2 should be at an equivalent version number
2 - it has to be checked that all packages that uses lignomeprint2.2
not only compile, but effectively work with the new version:
conglomerate, eog, evince, gal199, gal2.4, gedit, ggv, glade2,
gnumeric, gpdf, gthumb, gtksourceview, libgnomedb, librsvg2-mozilla,
librsvg2, gtk-sharp-monodoc, gtk-sharp, gtk-sharp2, gtksourceview-
sharp, gretl
Maybe better put it in your experimental tree, announce it on the
devel list, then all people can test it (I can make it for
conglomerate, evince, gedit, ggv, glade2, gtksourceview, libgnomedb,
in 10.- 4 stable (then it's likely it works also in 10.4-
transitional, for 10.3; Daniel Macks can test them) which I use
either directly or within my own packages.
Amicalement,
Michèle
<http://micmacfr.homeunix.org>
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
