Changes between Initial Version and Version 1 of MetapackagePolicy


Ignore:
Timestamp:
03/12/10 11:46:53 (13 years ago)
Author:
jdreed
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MetapackagePolicy

    v1 v1  
     1= DRAFT Policy for Metapackages = 
     2 
     3[[PageOutline]] 
     4 
     5== Core Metapackages == 
     6 
     7The core metapackages are: 
     8* debathena-standard 
     9* debathena-login 
     10* debathena-login-graphical 
     11* debathena-workstation 
     12* debathena-cluster 
     13 
     14TODO: -locker, -athena-libraries 
     15 
     16=== debathena-clients === 
     17 
     18The purpose of this package is to provide command-line client utilities.  Minimal configuration for those command-line client utilities should be provided, such that the client would not be useful without that configuration.   
     19 
     20=== debathena-standard === 
     21 
     22The purpose of this package is to provide a baseline of Athena functionality, suitable for users who prefer not to support logging in with Athena credentials into one's AFS homedir.  It should require debathena-clients, AFS, and the ability to run locker software.  It should recommend MIT site-specific configuration (such as relaying mail through the MIT outgoing servers). 
     23 
     24=== debathena-login === 
     25 
     26The purpose of this package is to ~~enable users to log in to tty sessions with their Athena credentials into their AFS home directories~~ create a headless remote-access server.  It should require debathena-standard as well as any functionality required to support logging in with Athena credentials into AFS home directories.  It should ~~recommend Athena-specific configuration packages for graphical software that the user may run (e.g. a web browser)~~. 
     27 
     28=== debathena-login-graphical === 
     29 
     30The purpose of this package is to add graphical console login functionality to debathena-login.  It should require debathena-login, as well as any software necessary for a local graphical login and any Athena-specific configuration for graphical applications.   It should recommend a robust graphical environment from the upstream OS. 
     31 
     32=== debathena-workstation === 
     33 
     34The purpose of this package is to configure an Athena workstation which requires minimal administration.  Automatic updates are provided, and the package should require all Athena software except for the Thirdparty package and any packages related to the cluster environment. 
     35 
     36=== debathena-cluster === 
     37 
     38The purpose of this package is to configure a workstation for the public IS&T-maintained cluster environment.  All Athena software is installed.  End users who wish to completely cede all control over their machines may install this package, but are not encouraged to do so for anything other than public/kiosk machines. 
     39 
     40 
     41== Supplemental Packages == 
     42 
     43Debathena provides two primary metapackages for the purpose of distributing software which complements the core Athena software. These two metapackages are: debathena-extra-software, and debathena-thirdparty.  These packages are further divided into smaller metapackages, including debathena-extra-software-nox, which is designed to be suitable for dialup servers, but these smaller metapackages are not normally designed to be installed by the _average_ end user.   
     44 
     45 
     46=== debathena-extra-software === 
     47 
     48The purpose of debathena-extra-software is provide Athena software that was historically "in the release" (i.e. installed locally). 
     49Software in this package should include, at a minimum: 
     50* a word processor/spreadsheet/presentation suite (e.g. OpenOffice.org) 
     51* a graphical mail client (e.g., Thunderbird) 
     52* a GUI multiprotocol chat application (e.g., pidgin) 
     53* Common window managers 
     54* a postscript viewer (e.g., gv) 
     55* packages required to build Debathena packages, including a standard OS build and packaging toolchain (build-essential, devscripts, debathena-build-depends) 
     56* postscript utilities (enscript, psutils) 
     57* emacs and vi 
     58* spell checkers 
     59* a full TeX/LaTeX distribution (e.g., texlive) 
     60* a text-mode web browser (e.g., links) 
     61* an NNTP client 
     62* common VCS clients 
     63 
     64==== Adding software to -extra-software ==== 
     65 
     66Since -extra-software is recommended by the installer, we have an obligation to keep it as small and streamlined as possible.  As such, 
     67there should be a very high barrier to entry for adding new packages.  
     68 
     69Any new packages should: 
     70 
     71* be useful to the Athena population as a whole, not just a small subset taking a specific class (i.e. Perl is useful to everyone, drscheme is useful to 6.001/6.034) 
     72* provide a balance between diversity and disk space/package count (i.e. Having 2 or 3 alternative window managers is helpful, having every single window manager ever is not) 
     73* not needlessly take sides in religious debates (i.e. if vi is included, emacs should be too) 
     74* be installable on all supported architectures (currently x86 and amd64) and all supported releases 
     75* be available in both Debian and Ubuntu without enabling repositories of questionable legality in the US (non-free, multiverse) 
     76 
     77=== debathena-thirdparty === 
     78 
     79The purpose of debathena-thirdparty is to provide local installations of what is historically referred to as "third party software".  Due to technical and licensing limitations, this currently only includes freely distributable software. 
     80 
     81thirdparty should have a lower barrier to entry than extra-software.  New packages added to -thirdparty needs simply to be useful to a 
     82significant subets of the Athena population (a specific class, forexample). 
     83 
     84The debathena-thirdparty package needs to be installable on all supported architectures. The use of architecture-specific dependencies 
     85is permissible but to be avoided if possible. The package also needs to be installable on the current release in use on the clusters and on the dialups.