Hello, Jeff!

On Tue, 2007-09-04 at 09:44 -0800, Jeff Spaleta wrote:
> The specific situation that I have been made aware of is when a
> codebase is licensed under GPLv2 without the optional "or later
> version" clause. This issue has actually prompted a change in how we
> communicate licensing summaries inside Fedora packaging, to try to
> help package maintainers stay ahead of any potential violations due to
> GPLv2 and GPLv3 conflicts. We're also trying to make sure we touc
> hbase with upstream developers has licensing changes are announced
> just to make sure this potential situation was considered fully.  If
> all the GPLv2 code you are making use of at build time has the "or
> later" clause then things should be okay. 

gPodder has started out with "GPLv2 or later", and all code
contributions are therefore upgradable to GPLv3.

As you raised the question and I was interested myself, I've checked the
copyright info for all dependencies (optional or strict) for the gPodder
Debian package (as this is what I package and use). I'm talking about
the current development version (in SVN), as 0.9.5 is still GPLv2:

python-gtk2: LGPL, version 2 or later
python-glade2: LGPL, version 2 or later
wget: GPL, version 2 or later (w/ OpenSSL exception)

Note that wget is only called using the "popen2" module (i.e. not
linked, but called and its output parsed by gPodder), but it would be
GPLv2 or later, anyway.

python-pymad: GPL, version 2
python-eyed3: GPL, version 2 or later

I don't know if pymad will become a problem, but if it does, simply
remove the dependency or if it's even impossible to distribute the
source this way, I can remove support for pymad, as the functionality
provided by pymad can also be provided by eyed3 or mplayer.

mplayer: GPL, version 2

But again, mplayer is only used through "os.popen", and only its stdout
output gets parsed by gPodder, so IIRC this is not considered "linking"
and therefore is no licensing problem(???).

Some points need to be clarified, mentioned above.


Thanks,
Thomas






_______________________________________________
gpodder-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/gpodder-devel

Reply via email to