[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 #36 from Mario Sanchez Prada <msanchez at igalia.com> 2011-06-03 11:07:21 EDT ---
(In reply to comment #34)
> I agree with Christophe that it shouldn't be a problem to build private static
> libraries and link them to the binary. As long as they are an exclusive part of
> the project this should be fine. 

Ok, it's obvious then (as per your comment and Christophe's) that I
misunderstood you in the first comments: I though having a .a file was actually
an issue. I'll probably change it at some point back to how it was before. Now
that flicksoup is no longer published independently, and that I've updated
references in wording inside frogr (and in live.gnome.org) that shouldn't be an
issue I guess.

> In order to emphasize flicksoup is an integral part of frogr and not intended
> to be used in third-party projects, I suggest to unify the source headers and
> release everything under GPLv3. Having differently licensed files might require
> some explanation (and an additional COPYING file with the LGPL license text in
> src/flicksoup ;-)). You can change the license back to LGPLv3 -- or whatever
> license you prefer -- once flicksoup is ready to become a separate project.

If putting a COPYING file inside src/flicksoup is good enough I'd go for this
approach, instead of changing the license of flicksoup files to GPLv3 now.

Btw, not sure at this point whether it would be still needed that I release
0.5.1 to ease life of Fedora packagers. Perhaps it's already clear enough that
flicksoup is not maintained separately :-), otherwise just ping me, give me
some time (cause I did this just in spare time), and I'll try to do it asap.

Thanks!

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