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

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

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

Revision 1.2 Revision 1.4
1GLEP: 52 1GLEP: 52
2Title: RESTRICT=interactive 2Title: RESTRICT=unattended
3Version: $Revision: 1.2 $ 3Version: $Revision: 1.4 $
4Last-Modified: $Date: 2006/10/14 02:47:31 $ 4Last-Modified: $Date: 2006/11/21 00:24:29 $
5Author: Marius Mauch <genone@gentoo.org>, 5Author: Marius Mauch <genone@gentoo.org>,
6Status: Draft 6Status: Draft
7Type: Standards Track 7Type: Standards Track
8Content-Type: text/x-rst 8Content-Type: text/x-rst
9Created: 13-Oct-2006 9Created: 13-Oct-2006
30 30
31Specification 31Specification
32============= 32=============
33 33
34Portage (and by extension other package managers) will support a new value for 34Portage (and by extension other package managers) will support a new value for
35the RESTRICT metadata variable called ``interactive``. This value may be used by 35the RESTRICT metadata variable called ``unattended``. This value may be used by
36the package manager and tools using its API to filter packages that require 36the package manager and tools using its API to filter packages that require
37interactive actions (for example to mask them in automated build environments). 37interactive actions (for example to mask them in automated build environments).
38How the package manager exactly reacts on the presence of this new flag is beyond 38How the package manager exactly reacts on the presence of this new flag is beyond
39this specification, but it's recommended to indicate it's presence to the user 39this specification, but it's recommended to indicate it's presence to the user
40whenever relevant. 40whenever relevant.
41 41
42This new setting should be used in ebuilds if it is known that they _typically_ 42This new setting should be used in ebuilds if it is known that they _typically_
43require user attention during the build process. If an ebuild just has a limited 43require user attention during the build process. If an ebuild just has a limited
44``risk`` of becoming interactive (like using the ``built_with_use`` function) 44``risk`` of becoming interactive (like using the ``built_with_use`` function)
45it shouldn't be restricted. 45it shouldn't be restricted. Note that only package installation is covered here,
46interactivity in package removals (in pkg_prerm and pkg_postrm) can not be
47indicated with this feature.
46 48
47Rationale 49Rationale
48========= 50=========
49 51
50The new RESTRICT=interactive metadata setting will give us the following benefits: 52The new RESTRICT=unattended metadata setting will give us the following benefits:
51 53
521. Enable masking of interactive ebuilds for automated build environments 541. Enable masking of interactive ebuilds for automated build environments
53 55
542. Metadata based searching for interactive ebuilds (superior to grep) 562. Metadata based searching for interactive ebuilds (superior to grep)
55 57

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

  ViewVC Help
Powered by ViewVC 1.1.20