Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/dvb-firmware: new package
Date: Wed, 28 Dec 2022 09:37:24 +0100	[thread overview]
Message-ID: <20221228093724.397df80e@windsurf> (raw)
In-Reply-To: <20221227215802.GC2498764@scaer>

Hello,

On Tue, 27 Dec 2022 22:58:02 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> > > +DVB_FIRMWARE_VERSION = 1.4.2
> > > +DVB_FIRMWARE_SITE = $(call github,LibreELEC,dvb-firmware,$(DVB_FIRMWARE_VERSION))
> > > +DVB_FIRMWARE_LICENSE = PROPRIETARY
> > > +DVB_FIRMWARE_REDISTRIBUTE = NO  
> > 
> > This DVB_FIRMWARE_REDISTRIBUTE = NO is not good, as it would actually
> > encourage people to violate the license of those firmware files. Indeed
> > what DVB_FIRMWARE_REDISTRIBUTE = NO says is "to not mention this
> > package in the manifest" and "do not copy the license files".  
> 
> Wrong. _REDISTRIBUTE = NO does not exclude the package from the manifest
> or from copying the license files; it only restricts copying the source
> tarball and the applied patches. The entry in the manifest is still
> added, and the license files are still copied.

Aaah, I didn't remember this. Thanks for the reminder! Then my point is
moot, I suppose (even though the fact that the package was missing
LICENSE_FILES in fact prevented the collection of license files into
legal-info).

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-12-28  8:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26 18:03 [Buildroot] [PATCH 1/1] package/dvb-firmware: new package Bernd Kuhls
2022-12-27 21:43 ` Thomas Petazzoni via buildroot
2022-12-27 21:58   ` Yann E. MORIN
2022-12-28  8:37     ` Thomas Petazzoni via buildroot [this message]
     [not found] ` <20221227224354.3b1d1fdf__40547.9438648158$1672177457$gmane$org@windsurf>
2022-12-27 22:30   ` Bernd Kuhls
2022-12-28 10:00     ` Thomas Petazzoni via buildroot
2022-12-28 22:22       ` Bernd Kuhls

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=20221228093724.397df80e@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd.kuhls@t-online.de \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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