Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Ulrich Mueller <ulm@g.o>
Subject: Re: Re: License groups in ebuilds
Date: Sat, 12 May 2012 21:49:42 +0200
>>>>> On Sat, 12 May 2012, Ciaran McCreesh wrote:

> On Sat, 12 May 2012 21:05:06 +0200
> Torsten Veller <tove@g.o> 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


References:
License groups in ebuilds
-- Ulrich Mueller
Re: License groups in ebuilds
-- Kent Fredric
Re: License groups in ebuilds
-- Torsten Veller
Re: Re: License groups in ebuilds
-- Ciaran McCreesh
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: License groups in ebuilds
Next by thread:
Re: License groups in ebuilds
Previous by date:
Re: RFC: Add new remote-id types in metadata.dtd
Next by date:
Re: License groups in ebuilds


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.