From: Kristian Fiskerstrand <k_f@gentoo.org>
To: gentoo-project@lists.gentoo.org, Rich Freeman <rich0@gentoo.org>
Subject: Re: [gentoo-project] What should the default acceptable licenses be?
Date: Tue, 29 Jan 2019 19:41:10 +0100 [thread overview]
Message-ID: <19f33ab8-fb98-275d-cea0-7a9710bf9f8e@gentoo.org> (raw)
In-Reply-To: <CAGfcS_mBxYu4T4PAv2na_Nhsm6yVKR=67u_u6MHptyFmsnoRmg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1173 bytes --]
On 1/29/19 7:27 PM, Rich Freeman wrote:
> Not depending on non-free software sounds nice in principle until you
> start talking about all those little things that make physical
> hardware actually work. If it were a practical option I'd be all for
> it. Otherwise this is a choice that really only exists on paper.
This is a matter of documentation in the handbook, though.
e.g on my laptop (all of my systems have similar setups already) which
has ACCEPT_LICENSE="-* @FREE -AGPL-3 -AGPL-3+ freedist ", the exception
list still only are has
# cat /etc/portage/package.license/*|wc -l
21
... of which 4 entries are related to AGPL and as such wouldn't really
be relevant for the proposed change. and that is a full desktop (laptop)
system, most systems have far less. In terms of linux-firmware, it
requires a simple two entries
sys-kernel/linux-firmware linux-firmware no-source-code
sys-kernel/gentoo-sources linux-firmware
.. but at least that gives specific knowledge of the non-free installs.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-29 18:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 21:04 [gentoo-project] What should the default acceptable licenses be? Kristian Fiskerstrand
2019-01-26 21:32 ` [gentoo-project] " Chí-Thanh Christopher Nguyễn
2019-01-27 9:47 ` Ulrich Mueller
2019-01-26 21:45 ` Thomas Deutschmann
2019-01-26 22:12 ` [gentoo-project] " Michał Górny
2019-01-26 22:51 ` Rich Freeman
2019-01-27 1:25 ` Alec Warner
2019-01-28 22:27 ` Matt Turner
2019-01-29 16:54 ` Thomas Deutschmann
2019-01-29 17:28 ` Brian Evans
2019-02-05 20:03 ` Roy Bamford
2019-01-29 17:53 ` Alec Warner
2019-01-29 18:27 ` Rich Freeman
2019-01-29 18:41 ` Kristian Fiskerstrand [this message]
2019-01-29 18:56 ` Kristian Fiskerstrand
2019-01-30 0:12 ` Thomas Deutschmann
2019-01-30 0:35 ` Alec Warner
2019-01-29 17:53 ` Rich Freeman
2019-01-31 16:53 ` Matt Turner
2019-02-05 23:47 ` [gentoo-project] " Kristian Fiskerstrand
2019-02-12 19:40 ` Alec Warner
2019-02-13 9:34 ` Thomas Deutschmann
2019-02-13 9:50 ` Kristian Fiskerstrand
2019-02-13 10:44 ` 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=19f33ab8-fb98-275d-cea0-7a9710bf9f8e@gentoo.org \
--to=k_f@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=rich0@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