/[gentoo]/xml/htdocs/proj/en/glep/glep-0023.txt
Gentoo

Diff of /xml/htdocs/proj/en/glep/glep-0023.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.1 Revision 1.3
1GLEP: 23 1GLEP: 23
2Title: Portage handling of ACCEPT_LICENSE 2Title: Portage handling of ACCEPT_LICENSE
3Version: $Revision: 1.1 $ 3Version: $Revision: 1.3 $
4Last-Modified: $Date: 2004/03/08 17:26:04 $ 4Last-Modified: $Date: 2004/10/26 00:21:28 $
5Author: Jason Stubbs <jstubbs@gentoo.org>, 5Author: Jason Stubbs <jstubbs@gentoo.org>,
6Status: Draft 6Status: Accepted
7Type: Standards Track 7Type: Standards Track
8Content-Type: text/x-rst 8Content-Type: text/x-rst
9Created: 9-Mar-2004 9Created: 9-Mar-2004
10Post-History: 8-Mar-2004 10Post-History: 8-Mar-2004 10-Mar-2004 25-Oct-2004
11 11
12 12
13Abstract 13Abstract
14======== 14========
15 15
16Currently, every ebuild in the portage tree is required to have a valid 16Currently, every ebuild in the portage tree is required to have a valid
17LICENSE entry. However, the syntax of this entry is not officially 17LICENSE entry. However, the syntax of this entry is not officially
18defined and the entry itself is only used when outputting package 18defined and the entry itself is only used when outputting package
19details. 19details.
20
21Status Update
22=============
23
24Repoman has been updated to check for the LICENSE syntax.
20 25
21 26
22Motivation 27Motivation
23========== 28==========
24 29
55functionality offered by a DEPEND string. To keep things simple, this 60functionality offered by a DEPEND string. To keep things simple, this
56GLEP proposes that the syntax be identical. For example: 61GLEP proposes that the syntax be identical. For example:
57 62
58:: 63::
59 64
60 LICENSE="mandatory-license \ 65 LICENSE="mandatory-license
61 ( || choosable-licence1 chooseable-license-2 ) \ 66 || ( choosable-licence1 chooseable-license-2 )
62 useflag? ( optional-component-license )" 67 useflag? ( optional-component-license )"
63 68
64 69
65License Groups 70License Groups
66-------------- 71--------------
67 72
68Almost all users are willing to install any software that is 73Almost all users are willing to install any software that is
69OSI-approved. Other users are willing to install any software and 74FSF-approved. Other users are willing to install any software and
70implicitly accept its license. To this end, portage will also need to 75implicitly accept its license. To this end, portage will also need to
71handle grouping of licenses. 76handle grouping of licenses.
72 77
73At a minimum, there needs to be the groups ``OSI-APPROVED`` and 78At a minimum, there needs to be the groups ``GPL-COMPATIBLE``,
74``NON-INTERACTIVE``. ``NON-INTERACTIVE`` licenses are those that don't 79``FSF-APPROVED``, ``OSI-APPROVED`` and ``NON-INTERACTIVE``.
75require interactive acceptance for it to be considered legally binding. 80``NON-INTERACTIVE`` licenses are those that don't require interactive
76This is the current behaviour of portage. 81acceptance for to be considered legally binding. This is the current
82behaviour of portage.
77 83
78 84
79ACCEPT_LICENSE 85ACCEPT_LICENSE
80-------------- 86--------------
81 87
92This GLEP proposes that the license group be prepended by the special 98This GLEP proposes that the license group be prepended by the special
93character "``@``". For example: 99character "``@``". For example:
94 100
95:: 101::
96 102
97 ACCEPT_LICENSE="-* @OSI-APPROVED" 103 ACCEPT_LICENSE="-* @FSF-APPROVED"
98 104
99 105
100Emerge Behaviour 106Emerge Behaviour
101---------------- 107----------------
102 108

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.3

  ViewVC Help
Powered by ViewVC 1.1.20