From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/4] libfm-extra: new package
Date: Wed, 10 Dec 2014 22:28:21 +0100 [thread overview]
Message-ID: <20141210212821.GI3926@free.fr> (raw)
In-Reply-To: <20141210221006.5ab0d254@free-electrons.com>
Thomas, All,
On 2014-12-10 22:10 +0100, Thomas Petazzoni spake thusly:
> On Wed, 10 Dec 2014 21:57:15 +0100, Yann E. MORIN wrote:
>
> > Also, the only file that seem to get compiled is:
> > src/extra/fm-xml-file.c
> >
> > for which the header states it is LGPLv2.1+.
> >
> > So, even if there's only the COPYING for the GPLv2 and that we only
> > compile an LGPLv2.1+ file, I'd state both licenses.
>
> I'm not sure here: since some files of the library are under the GPL,
> the library as a whole is under the GPL, even though some parts of it
> are under other licenses.
Yes, the GPL gobbles up the LGPL, because of its stronger requirements.
But licensing wise, they are both applicable licenses.
Even worse in this case, the resulting combination is probably just
LGPLv2.1+, since the only compiled file is LGPLv2.1+.
So, I'd prefer we stride on the safe side, and include both licenses,
and delegate to the user (and/or his legal team) the decision as to what
license is applicable.
We are not lawyer, and this is a complicated matter.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-12-10 21:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 15:33 [Buildroot] [PATCH v2 1/4] libfm-extra: new package Vicente Olivert Riera
2014-11-21 15:33 ` [Buildroot] [PATCH v2 2/4] menu-cache: " Vicente Olivert Riera
2014-12-10 21:05 ` Yann E. MORIN
2015-07-13 0:20 ` Thomas Petazzoni
2014-11-21 15:33 ` [Buildroot] [PATCH v2 3/4] libfm: " Vicente Olivert Riera
2014-12-10 21:18 ` Yann E. MORIN
2015-07-13 0:20 ` Thomas Petazzoni
2014-11-21 15:33 ` [Buildroot] [PATCH v2 4/4] pcmanfm: bump version to 1.2.3 Vicente Olivert Riera
2015-07-13 0:20 ` Thomas Petazzoni
2014-11-22 18:39 ` [Buildroot] [PATCH v2 1/4] libfm-extra: new package Thomas Petazzoni
2014-11-24 10:10 ` Vicente Olivert Riera
2014-11-24 19:33 ` Thomas Petazzoni
2014-11-25 9:52 ` Vicente Olivert Riera
2014-12-10 20:57 ` Yann E. MORIN
2014-12-10 21:10 ` Thomas Petazzoni
2014-12-10 21:28 ` Yann E. MORIN [this message]
2014-12-10 21:31 ` Thomas Petazzoni
2014-12-10 21:03 ` Yann E. MORIN
2015-07-13 0:19 ` Thomas Petazzoni
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=20141210212821.GI3926@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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