[mythtv] License

[Myth TV]

If I modify existing mythtv code and I want to distribute it, GPL is clear:
I've to make my new code GPL.
But even if I only supplement mythtv code (eg if I develop a new frontend
that uses mythtv libraries) I understand that GPL also forces me to release
my frontend code as GPL. I'm not completely sure at this point, I've read a
little and it seems to be a lot of stuff discussing if a program that
dynamically links to a library is a "derivative work" of that library or not
(and therefore, it falls under GPL's scope or not)

On Thu, Apr 2, 2009 at 2:09 PM, David Watkins <watkinshome at gmail.com> wrote:

> 2009/4/2 Myth TV <mythtvmythtv at gmail.com>:
> > Well....it matters if you are planning to develop a commercial STB, and
> you
> > dont't want your competitors to take any advantage from your work or your
> > ideas. That's the reason why I start this thread, we want to do things
> > right, we know and understand what opensource movement represents and we
> > want to respect GPL licenses. But would prefer not to release our changes
> > source code because of what I've said before and we were wondering if
> > there's any way to achieve it.
>
>
> I may be missing the point here but, provided you GPL the mythtv
> source code, then you can't you apply whatever restrictions you like
> on your own stuff?
>
> There's any nuumber of products that use GPL Linux with GPL
> applications but still contain propriertary code.  For example my
> Reciva radio runs GPL Linux, and GPL UPNP and Web servers, but also
> contains a licensed Realmedia player and other non open-source
> applications.
>
> I imagine your problems come if you want modify existing mythtv code,
> rather than supplement it.
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-dev/attachments/20090402/72582642/attachment.htm>