[gstreamer-bugs] [Bug 149102] New: - gstreamer license problems

[bugzilla-daemon at bugzilla.gnome.org]

http://bugzilla.gnome.org/show_bug.cgi?id=149102
GStreamer | gst-plugins | Ver: HEAD CVS

           Summary: gstreamer license problems
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: brian.cameron at sun.com
         QAContact: gstreamer-bugs at lists.sourceforge.net


I notice the following problems with various gstreamer plugin licenses:

* auparse says it is GPL when you run gst-inspect, but the code is all 
  LGPL.

* gstidct plugin says it is LGPL when you run gst-inspect, but the code
  for this plugin contains one file that uses the GPL license.

* gstvideo plugin says it is LGPL when you run gst-inspect, but the code
  for this plugin contains a file under the GPL license.

* texoverlay claims to be GPL, though the code all looks LGPL to me.

* monoscope claims to be GPL, though the code all looks LGPL to me.

* rtp claims to be LGPL, though it seems to contain GPL'ed code.


I suspect that most of these problems are simply that gst-inspect
needs to display the right value.  However, I think it is probably
a more serious problem that gstidct and gstvideo use GPL'ed code
and that these plugins are needed for the gstreamer framework to
work properly.

Also, another problem is that there is some inconsistancy regarding
plugins that are LGPL'ed but that depend on GPL'ed libraries.  It seems
that some plugins mark themselves as GPL in this case, and others mark
themselves as LGPL.  Which way is correct?  I'll highlight which plugins
have problems once that is settled.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.