| … | |
… | |
| 6 | PEP, see http://www.python.org/peps/pep-0001.html for instructions and links |
6 | PEP, see http://www.python.org/peps/pep-0001.html for instructions and links |
| 7 | to templates. DO NOT USE THIS HTML FILE AS YOUR TEMPLATE! |
7 | to templates. DO NOT USE THIS HTML FILE AS YOUR TEMPLATE! |
| 8 | --> |
8 | --> |
| 9 | <head> |
9 | <head> |
| 10 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> |
10 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> |
| 11 | <meta name="generator" content="Docutils 0.3.0: http://docutils.sourceforge.net/" /> |
11 | <meta name="generator" content="Docutils 0.3.3: http://docutils.sourceforge.net/" /> |
| 12 | <title>GLEP 15 -- Gentoo Script Repository</title> |
12 | <title>GLEP 15 -- Gentoo Script Repository</title> |
| 13 | <link rel="stylesheet" href="tools/glep.css" type="text/css" /> |
13 | <link rel="stylesheet" href="tools/glep.css" type="text/css" /> |
| 14 | </head> |
14 | </head> |
| 15 | <body bgcolor="white"> |
15 | <body bgcolor="white"> |
| 16 | <table class="navigation" cellpadding="0" cellspacing="0" |
16 | <table class="navigation" cellpadding="0" cellspacing="0" |
| … | |
… | |
| 20 | <img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]" |
20 | <img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]" |
| 21 | border="0" width="150" height="35" /></a></td> |
21 | border="0" width="150" height="35" /></a></td> |
| 22 | <td class="textlinks" align="left"> |
22 | <td class="textlinks" align="left"> |
| 23 | [<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>] |
23 | [<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>] |
| 24 | [<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>] |
24 | [<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>] |
| 25 | [<b><a href="http://www.gentoo.org/proj/en/glep/glep-0015.txt">GLEP Source</a></b>] |
25 | [<b><a href="./glep-0015.txt">GLEP Source</a></b>] |
| 26 | </td></tr></table> |
26 | </td></tr></table> |
| 27 | <div class="document"> |
27 | <div class="document"> |
| 28 | <table class="rfc2822 field-list" frame="void" rules="none"> |
28 | <table class="rfc2822 field-list" frame="void" rules="none"> |
| 29 | <col class="field-name" /> |
29 | <col class="field-name" /> |
| 30 | <col class="field-body" /> |
30 | <col class="field-body" /> |
| 31 | <tbody valign="top"> |
31 | <tbody valign="top"> |
| 32 | <tr class="field"><th class="field-name">GLEP:</th><td class="field-body">15</td> |
32 | <tr class="field"><th class="field-name">GLEP:</th><td class="field-body">15</td> |
| 33 | </tr> |
33 | </tr> |
| 34 | <tr class="field"><th class="field-name">Title:</th><td class="field-body">Gentoo Script Repository</td> |
34 | <tr class="field"><th class="field-name">Title:</th><td class="field-body">Gentoo Script Repository</td> |
| 35 | </tr> |
35 | </tr> |
| 36 | <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.2</td> |
36 | <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.4</td> |
| 37 | </tr> |
37 | </tr> |
| 38 | <tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference" href="http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/proj/en/glep/glep-0015.txt?cvsroot=gentoo">2003/10/13 11:00:20</a></td> |
38 | <tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference" href="http://www.gentoo.org/cgi-bin/viewcvs/xml/htdocs/proj/en/glep/glep-0015.txt?cvsroot=gentoo">2004/10/25 16:59:16</a></td> |
| 39 | </tr> |
39 | </tr> |
| 40 | <tr class="field"><th class="field-name">Author:</th><td class="field-body">James Harlow <hythloday at gentoo.org>,</td> |
40 | <tr class="field"><th class="field-name">Author:</th><td class="field-body">James Harlow <hythloday at gentoo.org>,</td> |
| 41 | </tr> |
41 | </tr> |
| 42 | <tr class="field"><th class="field-name">Status:</th><td class="field-body">Approved</td> |
42 | <tr class="field"><th class="field-name">Status:</th><td class="field-body">Approved</td> |
| 43 | </tr> |
43 | </tr> |
| 44 | <tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td> |
44 | <tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td> |
| 45 | </tr> |
45 | </tr> |
| 46 | <tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference" href="glep-0002.html">text/x-rst</a></td> |
46 | <tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference" href="glep-0012.html">text/x-rst</a></td> |
| 47 | </tr> |
47 | </tr> |
| 48 | <tr class="field"><th class="field-name">Created:</th><td class="field-body">30 Sep 2003</td> |
48 | <tr class="field"><th class="field-name">Created:</th><td class="field-body">30 Sep 2003</td> |
| 49 | </tr> |
49 | </tr> |
| 50 | <tr class="field"><th class="field-name">Post-History:</th><td class="field-body">30-Sep-2003</td> |
50 | <tr class="field"><th class="field-name">Post-History:</th><td class="field-body">30-Sep-2003, 25-Oct-2004</td> |
| 51 | </tr> |
51 | </tr> |
| 52 | </tbody> |
52 | </tbody> |
| 53 | </table> |
53 | </table> |
| 54 | <hr /> |
54 | <hr /> |
| 55 | <div class="contents topic" id="contents"> |
55 | <div class="contents topic" id="contents"> |
| 56 | <p class="topic-title"><a name="contents">Contents</a></p> |
56 | <p class="topic-title first"><a name="contents">Contents</a></p> |
| 57 | <ul class="simple"> |
57 | <ul class="simple"> |
| 58 | <li><a class="reference" href="#abstract" id="id2" name="id2">Abstract</a></li> |
58 | <li><a class="reference" href="#abstract" id="id2" name="id2">Abstract</a></li> |
|
|
59 | <li><a class="reference" href="#status-update" id="id3" name="id3">Status Update</a></li> |
| 59 | <li><a class="reference" href="#motivation" id="id3" name="id3">Motivation</a></li> |
60 | <li><a class="reference" href="#motivation" id="id4" name="id4">Motivation</a></li> |
| 60 | <li><a class="reference" href="#specification" id="id4" name="id4">Specification</a></li> |
61 | <li><a class="reference" href="#specification" id="id5" name="id5">Specification</a></li> |
| 61 | <li><a class="reference" href="#rationale" id="id5" name="id5">Rationale</a></li> |
62 | <li><a class="reference" href="#rationale" id="id6" name="id6">Rationale</a></li> |
| 62 | <li><a class="reference" href="#backwards-compatibility" id="id6" name="id6">Backwards Compatibility</a></li> |
63 | <li><a class="reference" href="#backwards-compatibility" id="id7" name="id7">Backwards Compatibility</a></li> |
| 63 | <li><a class="reference" href="#copyright" id="id7" name="id7">Copyright</a></li> |
64 | <li><a class="reference" href="#copyright" id="id8" name="id8">Copyright</a></li> |
| 64 | </ul> |
65 | </ul> |
| 65 | </div> |
66 | </div> |
| 66 | <div class="section" id="abstract"> |
67 | <div class="section" id="abstract"> |
| 67 | <h1><a class="toc-backref" href="#id2" name="abstract">Abstract</a></h1> |
68 | <h1><a class="toc-backref" href="#id2" name="abstract">Abstract</a></h1> |
| 68 | <p>There is currently no central repository for scripts that are useful |
69 | <p>There is currently no central repository for scripts that are useful |
| 69 | in administering a Gentoo system. This GLEP proposes a way to deal |
70 | in administering a Gentoo system. This GLEP proposes a way to deal |
| 70 | with this issue.</p> |
71 | with this issue.</p> |
| 71 | </div> |
72 | </div> |
|
|
73 | <div class="section" id="status-update"> |
|
|
74 | <h1><a class="toc-backref" href="#id3" name="status-update">Status Update</a></h1> |
|
|
75 | <p>Expect the first alpha release by the end of November or so.</p> |
|
|
76 | </div> |
| 72 | <div class="section" id="motivation"> |
77 | <div class="section" id="motivation"> |
| 73 | <h1><a class="toc-backref" href="#id3" name="motivation">Motivation</a></h1> |
78 | <h1><a class="toc-backref" href="#id4" name="motivation">Motivation</a></h1> |
| 74 | <p>There are many small tasks on a Gentoo system that can be made much |
79 | <p>There are many small tasks on a Gentoo system that can be made much |
| 75 | easier and fault-proof by scripting. However, not everyone has the |
80 | easier and fault-proof by scripting. However, not everyone has the |
| 76 | experience to write such scripts; those that do have the choice of |
81 | experience to write such scripts; those that do have the choice of |
| 77 | tracking down scripts on developer's webpages or with a search engine, |
82 | tracking down scripts on developer's webpages or with a search engine, |
| 78 | or writing them themselves, often duplicating effort that has been |
83 | or writing them themselves, often duplicating effort that has been |
| 79 | already done by other people.</p> |
84 | already done by other people.</p> |
| 80 | <p>A better solution would be to have a repository of these scripts on |
85 | <p>A better solution would be to have a repository of these scripts on |
| 81 | www.gentoo.org.</p> |
86 | www.gentoo.org.</p> |
| 82 | </div> |
87 | </div> |
| 83 | <div class="section" id="specification"> |
88 | <div class="section" id="specification"> |
| 84 | <h1><a class="toc-backref" href="#id4" name="specification">Specification</a></h1> |
89 | <h1><a class="toc-backref" href="#id5" name="specification">Specification</a></h1> |
| 85 | <p>A <a class="reference" href="mailto:scripts@gentoo.org">scripts@gentoo.org</a> email alias would be setup and forwarded to the team that |
90 | <p>A <a class="reference" href="mailto:scripts@gentoo.org">scripts@gentoo.org</a> email alias would be setup and forwarded to the team that |
| 86 | will accept and publish these scripts to the website. The team will need |
91 | will accept and publish these scripts to the website. The team will need |
| 87 | access to a portion of the website, but just enough to add the scripts, and |
92 | access to a portion of the website, but just enough to add the scripts, and |
| 88 | update links from the main "scripts" page. I would propose it be a |
93 | update links from the main "scripts" page. I would propose it be a |
| 89 | subproject of the tools or base top level project. The scripts team would |
94 | subproject of the tools or base top level project. The scripts team would |
| … | |
… | |
| 92 | <p>The scripts should be divided by type of task, for example sysadmin, |
97 | <p>The scripts should be divided by type of task, for example sysadmin, |
| 93 | gentooadmin, misc, and internally well-commented. If there are enough then |
98 | gentooadmin, misc, and internally well-commented. If there are enough then |
| 94 | it might be appropriate to have a search interface.</p> |
99 | it might be appropriate to have a search interface.</p> |
| 95 | </div> |
100 | </div> |
| 96 | <div class="section" id="rationale"> |
101 | <div class="section" id="rationale"> |
| 97 | <h1><a class="toc-backref" href="#id5" name="rationale">Rationale</a></h1> |
102 | <h1><a class="toc-backref" href="#id6" name="rationale">Rationale</a></h1> |
| 98 | <p>A repository on gentoo.org would address the problem of not having a |
103 | <p>A repository on gentoo.org would address the problem of not having a |
| 99 | central point where all the scripts reside; and as gentoo.org is |
104 | central point where all the scripts reside; and as gentoo.org is |
| 100 | trusted by most gentoo users, it would also solve the problem of |
105 | trusted by most gentoo users, it would also solve the problem of |
| 101 | running scripts without knowing their exact effect. Further trust |
106 | running scripts without knowing their exact effect. Further trust |
| 102 | could be generated by having developers sign their scripts and |
107 | could be generated by having developers sign their scripts and |
| … | |
… | |
| 106 | <p>Having a well-publicised script repository would also ease major |
111 | <p>Having a well-publicised script repository would also ease major |
| 107 | changes to the distribution, and could be a first line of defence to |
112 | changes to the distribution, and could be a first line of defence to |
| 108 | provide workarounds for security problems in packages.</p> |
113 | provide workarounds for security problems in packages.</p> |
| 109 | </div> |
114 | </div> |
| 110 | <div class="section" id="backwards-compatibility"> |
115 | <div class="section" id="backwards-compatibility"> |
| 111 | <h1><a class="toc-backref" href="#id6" name="backwards-compatibility">Backwards Compatibility</a></h1> |
116 | <h1><a class="toc-backref" href="#id7" name="backwards-compatibility">Backwards Compatibility</a></h1> |
| 112 | <p>Not a problem for this GLEP.</p> |
117 | <p>Not a problem for this GLEP.</p> |
| 113 | </div> |
118 | </div> |
| 114 | <div class="section" id="copyright"> |
119 | <div class="section" id="copyright"> |
| 115 | <h1><a class="toc-backref" href="#id7" name="copyright">Copyright</a></h1> |
120 | <h1><a class="toc-backref" href="#id8" name="copyright">Copyright</a></h1> |
| 116 | <p>This document has been placed in the public domain.</p> |
121 | <p>This document has been placed in the public domain.</p> |
| 117 | </div> |
122 | </div> |
| 118 | </div> |
123 | </div> |
| 119 | |
124 | |
| 120 | <hr class="footer"/> |
125 | <hr class="footer" /> |
| 121 | <div class="footer"> |
126 | <div class="footer"> |
| 122 | <a class="reference" href="glep-0015.txt">View document source</a>. |
127 | <a class="reference" href="glep-0015.txt">View document source</a>. |
| 123 | Generated on: 2004-01-13 20:40 UTC. |
128 | Generated on: 2004-10-25 16:52 UTC. |
| 124 | Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. |
129 | Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. |
| 125 | </div> |
130 | </div> |
| 126 | </body> |
131 | </body> |
| 127 | </html> |
132 | </html> |
| 128 | |
133 | |
Parent Directory
| 
Revision Log
| 
Patch