[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 #47 from Mario Sanchez Prada <msanchez at igalia.com> 2011-06-03 18:33:51 EDT ---
Created attachment 502924
  --> https://bugzilla.redhat.com/attachment.cgi?id=502924
Patches to be applied over frogr 0.5 for packaging

(In reply to comment #45)
> [...]
> I'm ok with that, but if it's ok to you, I'd like to help you by providing
> those specific patches to you in an organized way, after having squashed all
> those little commits I've been pushing lately, so handling them while packaging
> would not be a mess.
> 
> That way I would provide Fedora packagers a very easy way to package frogr in a
> Fedora compliant way.

I'll be away of a laptop during all the weekend and I don't know if someone
would like to do some work in the meanwhile about this... so now attaching a
tar.gz file with all the patches that would need to be applied to frogr 0.5
release according this conversation, and taking into account that flicksoup
files are being built again as an static file (see comment #46).

At the end the relevant patches are less and simpler than what I thought at
first:

  0001-Do-not-set-Wall-g0-and-02-flags-in-release-builds.patch
  0002-Updated-FSF-address-in-source-headers.patch
  0003-Added-Lesser-to-source-headers-where-missing.patch
  0004-Changed-wording-in-the-license-about-flicksoup.patch
  0005-Changed-wording-about-flicksoup-in-README-file.patch
  0006-Added-LGPLv3-COPYING-file-under-src-flicksoup-and-up.patch

Hope this helps to packagers this time. For the next release it wouldn't be
needed as all of them are already integrated upstream in master.

Have a nice weekend, and lots of thanks for the incredible feedback so far.

-- 
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.