| 1 |
Ryan Shaw wrote: |
| 2 |
> What should the LICENSE variable be set to when |
| 3 |
> creating an ebuild for software with a weird or |
| 4 |
> unknown license? |
| 5 |
|
| 6 |
That depends, LICENCSE="Foo" where "Foo" is a filename in |
| 7 |
/usr/portage/licenses/ . Foo should match the file name exactly. |
| 8 |
|
| 9 |
There is a special case called "as-is" please read it for details on it. |
| 10 |
|
| 11 |
If the licenses is truly unique then we need to add another one to the |
| 12 |
directory. |
| 13 |
|
| 14 |
If you need logic for more than one license use | for or logic and ( and |
| 15 |
) for grouping. And logic is implied if no other operator is used. eg: |
| 16 |
|
| 17 |
LICENSE="GPL-2 | ( LGPL-2.1 Foo )" |
| 18 |
|
| 19 |
The above would mean, The pacakges requires the user agreee to the GPL |
| 20 |
v2 licenser OR both of the LGPL v2.1 and Foo licenses. |
| 21 |
|
| 22 |
Sandy McArthur |
Archives