/[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.4
1GLEP: 23 1GLEP: 23
2Title: Portage handling of ACCEPT_LICENSE 2Title: Portage handling of ACCEPT_LICENSE
3Version: $Revision: 1.1 $ 3Version: $Revision: 1.4 $
4Last-Modified: $Date: 2004/03/08 17:26:04 $ 4Last-Modified: $Date: 2006/11/18 07:27:47 $
5Author: Jason Stubbs <jstubbs@gentoo.org>, 5Author: Jason Stubbs <jstubbs@gentoo.org>, Marius Mauch <genone@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 18-Nov-2006
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 20
21Status Update
22=============
23
24Repoman has been updated to check for the LICENSE syntax.
25A development portage branch with support for ACCEPT_LICENSE
26and license groups exists.
21 27
22Motivation 28Motivation
23========== 29==========
24 30
25Many users wish to regulate the software they install with regards to 31Many users wish to regulate the software they install with regards to
55functionality offered by a DEPEND string. To keep things simple, this 61functionality offered by a DEPEND string. To keep things simple, this
56GLEP proposes that the syntax be identical. For example: 62GLEP proposes that the syntax be identical. For example:
57 63
58:: 64::
59 65
60 LICENSE="mandatory-license \ 66 LICENSE="mandatory-license
61 ( || choosable-licence1 chooseable-license-2 ) \ 67 || ( choosable-licence1 chooseable-license-2 )
62 useflag? ( optional-component-license )" 68 useflag? ( optional-component-license )"
63 69
64 70
65License Groups 71License Groups
66-------------- 72--------------
67 73
68Almost all users are willing to install any software that is 74Almost all users are willing to install any software that is
69OSI-approved. Other users are willing to install any software and 75FSF-approved. Other users are willing to install any software and
70implicitly accept its license. To this end, portage will also need to 76implicitly accept its license. To this end, portage will also need to
71handle grouping of licenses. 77handle grouping of licenses.
72 78
73At a minimum, there needs to be the groups ``OSI-APPROVED`` and 79At a minimum, there needs to be the groups ``GPL-COMPATIBLE``,
74``NON-INTERACTIVE``. ``NON-INTERACTIVE`` licenses are those that don't 80``FSF-APPROVED``, ``OSI-APPROVED`` and ``NON-INTERACTIVE``.
75require interactive acceptance for it to be considered legally binding. 81``NON-INTERACTIVE`` licenses are those that don't require interactive
76This is the current behaviour of portage. 82acceptance for to be considered legally binding. This is the current
83behaviour of portage.
84
85These groups are defined in a new file ``license_groups`` in
86the ``profiles`` subdirectory of the tree (or overlays).
87The format of this file is
88
89::
90
91 <groupname> <license1> <license2> ... <licenseN>
92
93Also any line starting with # is ignored and may be used for comments.
94License groups may not contain negated elements, so a group
95
96::
97
98 mygroup foo -bar -bla
99
100is illegal.
77 101
78 102
79ACCEPT_LICENSE 103ACCEPT_LICENSE
80-------------- 104--------------
81 105
92This GLEP proposes that the license group be prepended by the special 116This GLEP proposes that the license group be prepended by the special
93character "``@``". For example: 117character "``@``". For example:
94 118
95:: 119::
96 120
97 ACCEPT_LICENSE="-* @OSI-APPROVED" 121 ACCEPT_LICENSE="-* @FSF-APPROVED"
98 122
123License groups may be negated with the result that all elements of that group
124are also negated.
99 125
100Emerge Behaviour 126Portage Behaviour
101---------------- 127-----------------
102 128
103At a minimum, emerge must handle unaccepted licenses the same way that 129Unaccepted licenses will be treated like any other masked package, that is
104it handles blockers. That is, with the --pretend flag the 130emerge will display a message listing any license that has to be accepted
105not-yet-accepted license should be listed in the output. Without the 131before the package can be merged with a pointer to the exact license text.
106--pretend flag, emerge should stop before any software is installed.
107 132
108This GLEP proposes that, unlike blockers, dependencies for software 133Past versions of this document proposed to handle license-masked packages
109should be checked regardless of license acceptance. Doing so will allow 134like blockers, but this would be inconsistent with other visibility
110the user to review all necessary licenses before initiating an actual 135filters as well as the current blocker system (as a blocker affects two
111emerge. 136packages) and be more complicated to implement.
112
113It is also proposed that the --ask option will display an unaccepted
114license and ask for acceptance, but not update any configuration files
115at this stage. Finally, the --verbose option should also list the
116licenses accepted for each package.
117
118 137
119Rationale 138Rationale
120========= 139=========
121 140
122An implementation of this proposal should make it easy for users wishing 141An implementation of this proposal should make it easy for users wishing
124 143
125 144
126Reference Implementation 145Reference Implementation
127======================== 146========================
128 147
129TODO 148Available in portage svn repository under main/branches/license-masking
130 149
131 150
132Backwards Compatibility 151Backwards Compatibility
133======================= 152=======================
134 153
135There should be no change to the user experience without the user 154There should be no change to the user experience without the user
136explicitly choosing to do so. This mandates that the 155explicitly choosing to do so. This mandates that the
137configuration variable be named ``ACCEPT_LICENSE`` as some users may 156configuration variable be named ``ACCEPT_LICENSE`` as some users may
138already have it set due to ebuilds using ``eutil.eclass``'s 157already have it set due to ebuilds using ``eutil.eclass``'s
139implementation. It also mandates that the default ``ACCEPT_LICENSE`` be 158implementation. It also mandates that the default ``ACCEPT_LICENSE`` be
140set to ``@NON-INTERACTIVE``. 159set to ``@NON-INTERACTIVE`` in the main gentoo repository as there will
141 160be no internal default in portage.
142 161
143References 162References
144========== 163==========
145 164
146.. [1] Gentoo Linux Bug 17367 165.. [1] Gentoo Linux Bug 17367

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

  ViewVC Help
Powered by ViewVC 1.1.20