[Bug 708765] Review Request: Frogr - Flickr Remote Organizer for GNOME

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=708765

--- Comment #17 from Mario Sanchez Prada <msanchez at igalia.com> 2011-05-31 16:44:13 EDT ---
(In reply to comment #15)
> [...]
> Right. Currently, we speak about v0.5, which doesn't ship the help files yet.
> Given the current state of the manual, you shouldn't think about a new release.
> We should concentrate the effort now to package the 0.5 release for F15 and
> Rawhide.

Yes, forget about it (see my previous comment)

> Moreover, I think about to provide a GTK+2 based version for F14. Is Frogr
> still fully compatible to GTK+2, or are there any constraints?

Yes, it's fully compatible (no constraints at all), actually the packages I
provide in my PPA for Ubuntu Lucid and Maverick are compiled with gtk2, while
in Ubuntu Natty the packe is compiled with gtk3.

The configure.ac is written so frogr will compile this way:

  * If gtk3 devel files are present, frogr will build with gtk3 (default).

  * If no gtk3 devel files are present, but gtk2 devel files are, frogr will
build with gtk2 (default fallback when gtk3 is not present).

  * If both gtk2 and gtk3 devel files installed frogr will build with gtk3.

  * If both gtk2 and gtk3 devel files installed, but you still want to force
using gtk2, you can pass --with-gtk=2.0 to the configure script.

So as you can see, gtk3 is the default but frogr will build with gtk2 perfectly
anyway, either by not having gtk3 dev files present or because you explicitly
say it so. About restrictions there are none of them since the code already
uses some #ifdef ... #endif regions to take into account the differences that
must be taken into account in frogr when it comes to using gtk2 or gtk3

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.