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

Contents of /xml/htdocs/proj/en/glep/glep-0015.txt

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.4 - (hide annotations) (download)
Mon Oct 25 16:59:16 2004 UTC (10 years ago) by g2boojum
Branch: MAIN
CVS Tags: HEAD
Changes since 1.3: +8 -3 lines
File MIME type: text/plain
update

1 liquidx 1.1 GLEP: 15
2     Title: Gentoo Script Repository
3 g2boojum 1.4 Version: $Revision: 1.3 $
4     Last-Modified: $Date: 2004/01/13 20:47:35 $
5 g2boojum 1.3 Author: James Harlow <hythloday@gentoo.org>,
6     Status: Approved
7 liquidx 1.1 Type: Standards Track
8     Content-Type: text/x-rst
9     Created: 30 Sep 2003
10 g2boojum 1.4 Post-History: 30-Sep-2003, 25-Oct-2004
11 liquidx 1.1
12    
13     Abstract
14     ========
15    
16     There is currently no central repository for scripts that are useful
17     in administering a Gentoo system. This GLEP proposes a way to deal
18     with this issue.
19    
20 g2boojum 1.4 Status Update
21     =============
22    
23     Expect the first alpha release by the end of November or so.
24    
25 liquidx 1.1 Motivation
26     ==========
27    
28     There are many small tasks on a Gentoo system that can be made much
29     easier and fault-proof by scripting. However, not everyone has the
30     experience to write such scripts; those that do have the choice of
31     tracking down scripts on developer's webpages or with a search engine,
32     or writing them themselves, often duplicating effort that has been
33     already done by other people.
34    
35 liquidx 1.2 A better solution would be to have a repository of these scripts on
36     www.gentoo.org.
37 liquidx 1.1
38     Specification
39     =============
40    
41     A scripts@gentoo.org email alias would be setup and forwarded to the team that
42     will accept and publish these scripts to the website. The team will need
43     access to a portion of the website, but just enough to add the scripts, and
44     update links from the main "scripts" page. I would propose it be a
45     subproject of the tools or base top level project. The scripts team would
46     need commit access to gentoo/xml/htdocs/proj/en/[base|tools]/scripts/.It
47     shouldn't increase the load on gentoo.org significantly.
48    
49 liquidx 1.2 The scripts should be divided by type of task, for example sysadmin,
50     gentooadmin, misc, and internally well-commented. If there are enough then
51     it might be appropriate to have a search interface.
52 liquidx 1.1
53     Rationale
54     =========
55    
56     A repository on gentoo.org would address the problem of not having a
57     central point where all the scripts reside; and as gentoo.org is
58     trusted by most gentoo users, it would also solve the problem of
59     running scripts without knowing their exact effect. Further trust
60     could be generated by having developers sign their scripts and
61     uploading the signatures in parallel.
62    
63     Periodically, a snapshot could be taken of the repository, the scripts
64     QA'd, and a package made and distributed.
65    
66     Having a well-publicised script repository would also ease major
67     changes to the distribution, and could be a first line of defence to
68     provide workarounds for security problems in packages.
69    
70     Backwards Compatibility
71     =======================
72    
73     Not a problem for this GLEP.
74    
75    
76     Copyright
77     =========
78    
79     This document has been placed in the public domain.

  ViewVC Help
Powered by ViewVC 1.1.20