public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: License groups in ebuilds
Date: Sat, 12 May 2012 21:49:42 +0200	[thread overview]
Message-ID: <20398.48854.238079.577401@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20120512201250.6f754739@googlemail.com>

>>>>> On Sat, 12 May 2012, Ciaran McCreesh wrote:

> On Sat, 12 May 2012 21:05:06 +0200
> Torsten Veller <tove@gentoo.org> wrote:
>> The perl-module.eclass offers a default LICENSE as
>> LICENSE="${LICENSE:-|| ( Artistic GPL-1 GPL-2 GPL-3 )}"
>> 
>> So if a distribution uses "the same license as Perl 5 itself" you can
>> just drop the LICENSE from the ebuild (as long no former eclass sets
>> its own LICENSE).

> That's definitely not going to work if the 'inherit' comes at the top
> of the ebuild, and is severely dodgy if it doesn't...

I have to agree with Ciaran. The eclass should simply assign LICENSE
unconditionally. Ebuilds can override it if necessary.

And if an ebuild inherits two eclasses that both define LICENSE, then
it's probably better if the ebuild contains its own explicit
definition.

Ulrich



  parent reply	other threads:[~2012-05-12 19:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10  9:39 [gentoo-dev] License groups in ebuilds Ulrich Mueller
2012-05-10  9:57 ` Kent Fredric
2012-05-12 19:05   ` [gentoo-dev] " Torsten Veller
2012-05-12 19:12     ` Ciaran McCreesh
2012-05-12 19:49       ` Torsten Veller
2012-05-12 19:49       ` Ulrich Mueller [this message]
2012-06-16 17:49 ` [gentoo-dev] " Sebastian Pipping
2012-06-16 18:16   ` Ulrich Mueller
2012-09-14 23:35     ` Ulrich Mueller
2012-09-18  6:10       ` 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=20398.48854.238079.577401@a1i15.kph.uni-mainz.de \
    --to=ulm@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