1 |
>>>>> On Sat, 12 May 2012, Ciaran McCreesh wrote: |
2 |
|
3 |
> On Sat, 12 May 2012 21:05:06 +0200 |
4 |
> Torsten Veller <tove@g.o> wrote: |
5 |
>> The perl-module.eclass offers a default LICENSE as |
6 |
>> LICENSE="${LICENSE:-|| ( Artistic GPL-1 GPL-2 GPL-3 )}" |
7 |
>> |
8 |
>> So if a distribution uses "the same license as Perl 5 itself" you can |
9 |
>> just drop the LICENSE from the ebuild (as long no former eclass sets |
10 |
>> its own LICENSE). |
11 |
|
12 |
> That's definitely not going to work if the 'inherit' comes at the top |
13 |
> of the ebuild, and is severely dodgy if it doesn't... |
14 |
|
15 |
I have to agree with Ciaran. The eclass should simply assign LICENSE |
16 |
unconditionally. Ebuilds can override it if necessary. |
17 |
|
18 |
And if an ebuild inherits two eclasses that both define LICENSE, then |
19 |
it's probably better if the ebuild contains its own explicit |
20 |
definition. |
21 |
|
22 |
Ulrich |