public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Russel Winder <russel@winder.org.uk>
To: DVB_Linux_Media <linux-media@vger.kernel.org>
Subject: libdvbv5 licencing
Date: Sat, 26 Mar 2016 06:13:08 +0000	[thread overview]
Message-ID: <1458972788.3344.8.camel@winder.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

I hadn't noticed previously, but it has been brought to my attention
that libdvbv5 is licenced as GPLv2. This makes it impossible
(effectively) for any non-GPL code to make use of libdvbv5. This seems
to undermine the whole point of libdvbv5. 

In particular, I wanted to rip out all the Linux API based code from
the GStreamer DVB plugins and replace it with use of libdvbv5. However
because of the licencing (GStreamer is LGPL and must only use LGPL or
more liberal licenced code), this is going to be impossible.

Instead of ripping out the current code (which is DVBv3) and using
libdvbv5, it looks like I will be forced to recreate libdvbv5 but as
LGPL code.

Is there any chance of relicencing libdvbv5 as LGPL code so that others
may use it?

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net
41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2016-03-26  6:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-26  6:13 Russel Winder [this message]
2016-04-12 14:19 ` libdvbv5 licencing Mauro Carvalho Chehab
2016-04-13 15:40   ` Russel Winder
2016-04-19 19:36     ` Mauro Carvalho Chehab
2016-04-22  8:25       ` Russel Winder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1458972788.3344.8.camel@winder.org.uk \
    --to=russel@winder.org.uk \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox