[MacPorts] #26710: Update gdk-pixbuf to latest release

[David Evans]

 On 10/3/10 1:24 PM, Rainer Müller wrote:
> On 2010-10-03 20:16 , David Evans wrote:
>> Actually the latest version of gtk+ 2.22.0 breaks gdk-pixbuf out
>> separately again (also 2.22.0) to keep
>> it out of the gtk3 development path.  So a gdk-pixbuf-2 port will be
>> necessary when gtk2 is upgraded (and some
>> logic to disable the old gtk2 before upgrading to avoid conflicts
>> between the old and new systems).  Perhaps
>> this is what the OP is referring to?
> Ahhh, this explains what's going on here. Yes, I would also go for a new
> port name as gdk-pixbuf still has dependents.
>
> So we definitely need a gdk-pixbuf2 port and have multiple options to
> implement this at the time gtk2 gets updated to 2.22.0:
>
> a) gtk2 @0.22.0 adds a dependency on gdk-pixbuf2
>
>    Complicated upgrade path, as gdk-pixbuf2 needs to replace files from
>    gtk2 <0.22.0. The upgrade will not be straight forward, but could be
>    done with some hack inside a pre-activate phase in gdk-pixbuf2.
>
>
> b) gtk2 @0.22.0 does *not* add a dependency on gdk-pixbuf2, but
>    this is added to individual ports
>
>    Easy upgrade path, but a lot of work as this means scanning all
>    recursive dependents of gtk2 for linkage with libgdk-pixbuf*.dylib.
>
>
> Rainer
>
In spite of the separation, gtk2 0.22.0 DOES depend on gdk-pixbuf2 >=
0.22.0 and
fails configure if the old gtk2 is active so my thought was

    gtk2 adds dependency on gdk-pixbuf2

    gdk-pixbuf2 does a check for installed gdk-pixbuf2/gtk2 < 0.22.0 and
if found
    asks the user to deactivate the old gtk2 port before proceeding and
then install
    the new gtk2. 

    Of course, gdk-pixbug2 conflicts with the older gtk2 with embedded
gdk-pixbuf
    so the two ports need to be committed at the same time

Apparently the point of the separation is that the developers don't
intend to do any
further changes to gdk-pixbuf as part of the gtk3 effort and so they
don't want to
have to have it become gdk-pixbuf-3 just because it is included in gtk+.