public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <webmaster@hartwork.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Add operator + for licenses (EAPI-4 ?)
Date: Fri, 04 Sep 2009 23:11:14 +0200	[thread overview]
Message-ID: <4AA18272.7070509@hartwork.org> (raw)
In-Reply-To: <4AA03037.7000203@gentoo.org>

Mounir Lamouri wrote:
>> However I do notice that "GPL-2+" could make things easier.
>> Why not introduce a license group for it like @GPL-2+ or so, instead?
>> That would be transparent and use existing means.
>>   
> I don't understand where the black magic is.

It would be in the implementation and in the non-transparency.
How can a user understabnd that "GPL-2+" refers to a group of license
files but "GPL-2" refers to a single file?  He may guess but it's not
obvious, especially if it hasn#t been like that in the past, which is
the case.


> However, a
> group will not add the information in the ebuild. In other words, I will
> have GPL-2 and GPL-3 with GPL-2+ in ACCEPT_LICENSE but I will not have
> GPL-2+ packages if i set only GPL-3 in ACCEPT_LICENSE.

I propose support for license groups in ebuilds then, I guess.



Sebastian



  reply	other threads:[~2009-09-04 21:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31 22:12 [gentoo-dev] [RFC] Add operator + for licenses (EAPI-4 ?) Mounir Lamouri
2009-08-31 22:30 ` Rémi Cardona
2009-09-03 20:50   ` Mounir Lamouri
2009-09-01  2:21 ` Sebastian Pipping
2009-09-01  5:54   ` [gentoo-dev] " Duncan
2009-09-03 21:10     ` Mounir Lamouri
2009-09-03 21:15       ` Rémi Cardona
2009-09-03 21:27         ` Mounir Lamouri
2009-09-04  4:53           ` Duncan
2009-09-04 15:01           ` Rémi Cardona
2009-09-04 18:52             ` David Leverton
2009-09-04 20:04               ` Rémi Cardona
2009-09-04 20:08                 ` Ciaran McCreesh
2009-09-05 14:03                   ` Maciej Mrozowski
2009-09-05 15:02                     ` Ciaran McCreesh
2009-09-06  0:34                     ` Thomas Anderson
2009-09-06  6:31                       ` Rémi Cardona
2009-09-03 21:08   ` [gentoo-dev] " Mounir Lamouri
2009-09-04 21:11     ` Sebastian Pipping [this message]
2009-09-05  1:06       ` Zac Medico
2009-09-05  8:40         ` [gentoo-dev] " Duncan
2009-09-05  9:28         ` [gentoo-dev] " Ulrich Mueller
2009-09-05 10:59           ` Zac Medico
2009-09-05 17:21         ` Mounir Lamouri
2009-09-05 18:41           ` Ulrich Mueller
2009-09-06  0:14             ` Sebastian Pipping
2009-09-05 21:37           ` Zac Medico
2009-10-01  2:01         ` Sebastian Pipping
2009-10-01 13:09           ` volkmar
2009-09-04 15:47 ` Jeremy Olexa

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=4AA18272.7070509@hartwork.org \
    --to=webmaster@hartwork.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