Changes between Version 2 and Version 3 of MetapackagePolicy
- Timestamp:
- 03/30/10 11:34:02 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MetapackagePolicy
v2 v3 69 69 Any new packages should: 70 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)71 * be useful to the Athena population as a whole, not just a small subset taking a specific class (e.g. Perl is useful to everyone, drscheme is useful to 6.001/6.034) 72 * provide a balance between diversity and disk space/package count (e.g. 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 (e.g. if vi is included, emacs should be too) 74 74 * be installable on all supported architectures (currently x86 and amd64) and all supported releases 75 75 * be available in both Debian and Ubuntu without enabling repositories of questionable legality in the US (non-free, multiverse) … … 80 80 81 81 thirdparty should have a lower barrier to entry than extra-software. New packages added to -thirdparty needs simply to be useful to a 82 significant sub ets of the Athena population (a specific class, forexample).82 significant subsets of the Athena population (a specific class, for example). 83 83 84 84 The debathena-thirdparty package needs to be installable on all supported architectures. The use of architecture-specific dependencies