Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Yunhao Tian <t123yh.xyz@gmail.com>,
	Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/libopenaptx: drop package
Date: Tue, 21 Dec 2021 22:19:14 +0100	[thread overview]
Message-ID: <20211221211914.GK2603@scaer> (raw)
In-Reply-To: <62ca9c6d-42c5-d5b4-c423-6d050fdf6ae1@mind.be>

Arnout, All,

On 2021-12-20 23:30 +0100, Arnout Vandecappelle spake thusly:
> On 20/12/2021 23:08, Yann E. MORIN wrote:
[--SNIP--]
> >However, the LGPLv2.1+ does not allow one to *strip* the code of its
> >license and *replace* it with another license, even if the LGPLV2.1+ can
> >be "upgraded" to that other license.
> 
>  Yes it does. As I wrote, section 3:
[--SNIP--]
> I.e. anyone (not the copyright holders, but anyone) can apply GPL-2.0+ to
> the code instead of LGPL-2.1+ and continue distributing it under GPL-2.0+.
> Note the irreversible as well.

Indeed. This is something that completely eluded me. Thanks for poking
it at my nose! :-)

[--SNIP--]
>  Bottom line: *we're* definitely doing nothing wrong by keeping the package,
> and I don't think we're creating problems for our users either. We're
> creating more problems by removing the package, IMHO.

OK-ish.

Though, if we were to roll back to 0.2.0, or switch to the 0.2.0-forked
libfreeaptx, we would not have any issue.

Thanks for bearing with me.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-12-21 21:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-19 11:04 [Buildroot] [PATCH] package/libopenaptx: drop package Yann E. MORIN
2021-12-19 11:39 ` Yunhao Tian
2021-12-20 20:36 ` Arnout Vandecappelle
2021-12-20 22:08   ` Yann E. MORIN
2021-12-20 22:30     ` Arnout Vandecappelle
2021-12-21 21:19       ` Yann E. MORIN [this message]
2021-12-21 21:46         ` Arnout Vandecappelle

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=20211221211914.GK2603@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=t123yh.xyz@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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