public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Steven J. Long" <slong@rathaus.eclipse.co.uk>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] Re: changing the default of ACCEPT_LICENSE in portage
Date: Thu, 25 Jul 2013 21:29:40 +0100	[thread overview]
Message-ID: <20130725202940.GA8481@rathaus.eclipse.co.uk> (raw)
In-Reply-To: <51F1717D.1090301@gentoo.org>

hasufell wrote:
> Matthew Thode wrote:
> > hasufell wrote:
> >> Gentoo has a social contract [1] which makes a lot of noise about
> >> free software. However our default settings allow to use almost
> >> any kind of non-free license such as "all-rights-reserved".
> >> 
> >> While I see nothing wrong with gentoo providing proprietary stuff
> >> (and I have created a lot of such games ebuilds), I think
> >> according to our philsophy and social contract we should make
> >> people aware of free software and because of that also change the
> >> default to:
> >> 
> >> ACCEPT_LICENSE="@FREE"
> >> 
> >> This is only about the _default_. We will have to change the
> >> handbook at "1.d. Licenses" [2] and might also make a news item.
> >> 
> > This is what I thought the default license group already was, I'm
> > all for it :D
> 
> The default is currently:
> 
> ACCEPT_LICENSE:"* -@EULA"
> 
> in /usr/share/portage/config/make.globals

This is reasonable, but can we have the above old-default commented out in make.conf,
above the new setting? That way things are transparent, and users who want to switch
to using non-free can do so easily without the EULA stuff being pulled in, aiui it
would be if users simply put "*" in there.

After all, as you yourself wrote about:
> adding a line such as: ACCEPT_LICENSE="*"
..users are likely to reach for that by default, too, when they shouldn't accept
@EULA generically, but via package.license.

Chí-Thanh Christopher Nguyễn wrote:
> Also this would affect the kernel sources when deblobbing is disabled.
>
> I am not against this move, but this will require a lot of effort in
> educating users about the consequences.

Presumably stages have been built, and machines installed using just @FREE? I'd just
like assurance that these "consequences" are known not to affect a standard desktop
install, or that this will be tested thoroughly before the switch, in which case it
is not, one would hope, imminent.

Regards,
steveL
-- 
#friendly-coders -- We're friendly, but we're not /that/ friendly ;-)



  reply	other threads:[~2013-07-25 20:29 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 18:31 [gentoo-project] changing the default of ACCEPT_LICENSE in portage hasufell
2013-07-25 18:41 ` Matthew Thode
2013-07-25 18:42   ` hasufell
2013-07-25 20:29     ` Steven J. Long [this message]
2013-07-25 20:50       ` [gentoo-project] " hasufell
2013-07-30  1:48         ` [gentoo-project] " Steven J. Long
2013-07-25 18:51 ` [gentoo-project] " Alexander Berntsen
2013-07-25 18:56 ` [gentoo-project] " Pacho Ramos
2013-07-25 18:58   ` Matt Turner
2013-07-25 19:07     ` Pacho Ramos
2013-07-25 19:16       ` hasufell
2013-07-25 19:30         ` Pacho Ramos
2013-07-25 20:47           ` hasufell
2013-07-25 18:58   ` hasufell
2013-07-25 19:52 ` Chí-Thanh Christopher Nguyễn
2013-07-25 20:42   ` hasufell
2013-07-25 20:59     ` Chí-Thanh Christopher Nguyễn
2013-07-25 21:04       ` Ulrich Mueller
2013-07-25 21:12         ` Chí-Thanh Christopher Nguyễn
2013-07-25 21:21           ` Alexander Berntsen
2013-07-26  6:18           ` Ulrich Mueller
2013-07-28 17:51           ` Ulrich Mueller
2013-07-29 21:35             ` Chí-Thanh Christopher Nguyễn
2013-07-29 21:53               ` Alexander Berntsen
2013-07-29 21:57               ` Andreas K. Huettel
2013-07-25 20:52   ` Ulrich Mueller
2013-07-25 20:16 ` Dirkjan Ochtman
2013-07-25 20:21   ` Ian Stakenvicius
     [not found] ` <20130726184824.538e4d74@melee>
2013-07-26 18:44   ` [gentoo-project] " Alexander Berntsen
2013-07-26 20:50     ` Matt Turner
2013-07-26 20:56       ` Ciaran McCreesh
2013-07-26 21:16       ` Alexander Berntsen
2013-07-26 21:32         ` Rick "Zero_Chaos" Farina
2013-07-26 22:15     ` Michał Górny
2013-07-30 15:08 ` [gentoo-project] " Donnie Berkholz
2013-07-30 15:28   ` hasufell
2013-07-30 15:56     ` Zac Medico
2013-07-30 16:03       ` Zac Medico
2013-07-30 16:15     ` Matt Turner
2013-07-30 23:17     ` Jeroen Roovers
2013-07-31 11:27       ` Andreas K. Huettel
2013-07-31 11:30         ` hasufell
2013-07-31 11:33           ` Ciaran McCreesh
2013-07-31 11:46           ` Andreas K. Huettel
2013-07-31 11:50             ` hasufell
2013-07-31 15:18               ` Rich Freeman
2013-07-31 15:25                 ` Jeff Horelick
2013-07-31 16:07                   ` Ian Stakenvicius
2013-07-31 17:09                     ` Zac Medico
2013-07-31 17:56                     ` Rich Freeman
2013-07-31 19:58                     ` Ulrich Mueller
2013-07-31 20:00                       ` Ian Stakenvicius
2013-07-31 20:19                         ` Ulrich Mueller
2013-07-31 20:02                       ` Rich Freeman
2013-07-31 16:06                 ` Ulrich Mueller
2013-07-30 16:09   ` Ulrich Mueller
2013-07-30 16:13     ` Ciaran McCreesh
2013-07-30 16:16       ` hasufell
2013-08-01  9:32 ` Andreas K. Huettel

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=20130725202940.GA8481@rathaus.eclipse.co.uk \
    --to=slong@rathaus.eclipse.co.uk \
    --cc=gentoo-project@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