From: Aaron Bauman <bman@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: News item for review: Change of ACCEPT_LICENSE default (v3)
Date: Thu, 16 May 2019 05:28:51 -0400 [thread overview]
Message-ID: <20190516092851.GB26066@beaners> (raw)
In-Reply-To: <w6gtvduhjox.fsf_-_@kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 2428 bytes --]
On Thu, May 16, 2019 at 10:45:02AM +0200, Ulrich Mueller wrote:
> Another iteration, due to an upcoming restructuring of the
> linux-firmware package. Only change in v3 is the second line in the
> package.license file which now contains the @BINARY-REDISTRIBUTABLE
> group instead of individual licenses.
>
> Current plan is that this will go live on next Sunday, 2019-05-19.
>
>
> Title: Change of ACCEPT_LICENSE default
> Author: Ulrich Müller <ulm@gentoo.org>
> Posted: 2019-05-19
> Revision: 1
> News-Item-Format: 2.0
>
> The default set of accepted licenses has been changed [1,2] to:
>
> ACCEPT_LICENSE="-* @FREE"
>
> This means that by default only free software and documentation
> will be installable. The "FREE" license group is defined in the
> profiles/license_groups file in the Gentoo repository. It contains
> licenses that are explicitly approved by the Free Software Foundation,
> the Open Source Initiative, or that follow the Free Software
> Definition.
>
> The system wide default for the accepted licenses is controlled by
> the ACCEPT_LICENSE variable in /etc/portage/make.conf, or it can be
> specified on a per-package basis in /etc/portage/package.license.
>
> For example, to allow the app-arch/unrar and sys-kernel/linux-firmware
> packages to be installed, the following lines would have to be added
> to /etc/portage/package.license:
>
> app-arch/unrar unRAR
> sys-kernel/linux-firmware @BINARY-REDISTRIBUTABLE
>
> If you want to revert to the previous default, add the following line
> to /etc/portage/make.conf:
>
> ACCEPT_LICENSE="* -@EULA"
>
> This will permit all licenses, except End User License Agreements that
> require reading and signing an acceptance agreement. Note that this
> will also accept non-free software and documentation.
>
> See GLEP 23 [3] as well as the make.conf(5) and portage(5) man pages
> for the detailed syntax of the ACCEPT_LICENSE variable. Further
> information about licenses can be found in the Gentoo Handbook [4]
> and on the license groups wiki page [5].
>
> [1] https://projects.gentoo.org/council/meeting-logs/20190210-summary.txt
> [2] https://bugs.gentoo.org/676248
> [3] https://www.gentoo.org/glep/glep-0023.html
> [4] https://wiki.gentoo.org/wiki/Handbook:AMD64/Working/Portage#Licenses
> [5] https://wiki.gentoo.org/wiki/License_groups
lgtm
--
Cheers,
Aaron
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-16 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 8:11 [gentoo-dev] News item for review: Change of ACCEPT_LICENSE default Ulrich Mueller
2019-04-24 3:56 ` Aaron Bauman
2019-04-25 9:14 ` [gentoo-dev] Re: News item for review: Change of ACCEPT_LICENSE default (v2) Ulrich Mueller
2019-05-16 8:45 ` [gentoo-dev] Re: News item for review: Change of ACCEPT_LICENSE default (v3) Ulrich Mueller
2019-05-16 9:28 ` Aaron Bauman [this message]
2019-05-21 19:23 ` [gentoo-dev] News item for review: Change of ACCEPT_LICENSE default (v4) Ulrich Mueller
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=20190516092851.GB26066@beaners \
--to=bman@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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