| 1 |
|
| 2 |
NOTE: In these lists, package names should be on one line by itself. |
| 3 |
No spaces/tabs/comments on the same line. |
| 4 |
|
| 5 |
cpp does not remove spaces/tabs, and perl apparently considers literally |
| 6 |
everything between \n and \n as package name. So, it's best to have no |
| 7 |
spaces/tabs at all outside the comment delimiters. |
| 8 |
|
| 9 |
The exclude/unexclude lists are NOT preprocessed, so comments there are |
| 10 |
not supported. |
| 11 |
|
| 12 |
----- |
| 13 |
|
| 14 |
THE "USEFUL CD 1 PROJECT" RATIONALE J.A. Bezemer, Jan-Apr 2001 |
| 15 |
[email protected] |
| 16 |
|
| 17 |
Quite many Debian users do not have the Complete Official CD set, but only |
| 18 |
one (or sometimes two) CDs. They expect that CD to be as useful as |
| 19 |
possibe, that is, to contain as much useful packages as possible. |
| 20 |
|
| 21 |
We have four means to determine the usefulness of a (set of) package(s): |
| 22 |
the Popularity Contest (see above), the task-* packages, packages included |
| 23 |
on the official CDs of other distributions, and our own experience. |
| 24 |
|
| 25 |
We can distinguish two main groups of people that will use a single Debian CD: |
| 26 |
1. People paying nothing |
| 27 |
2. People wanting to pay as little as possible |
| 28 |
|
| 29 |
ad 1. This happens mostly at tradeshows/expos/conferences. We can further |
| 30 |
subdivide this group into two opposites: |
| 31 |
a. Complete Linux newbies that want to use Debian as their first |
| 32 |
distribution. |
| 33 |
b. Well-experienced Linux users that want to compare Debian to other |
| 34 |
distributions, mostly with the pre-determined intent to either switch |
| 35 |
to the "best" distribution for their own personal use, or employ the |
| 36 |
"best" distribution for some specific project in their company. |
| 37 |
|
| 38 |
ad 2. This occurs mostly by people ordering CDs from regular vendors. |
| 39 |
While groups a. and b. are also present here, there is another group that |
| 40 |
deserves attention: |
| 41 |
c. Relatively experienced Debian users with a reasonably fast and cheap |
| 42 |
Internet connection that order CD1 to get the bulk of the upgrades, and |
| 43 |
fetch the rest from online repositories. |
| 44 |
|
| 45 |
The mentioned groups each have specific expectations from their single CD. |
| 46 |
|
| 47 |
ad a. Newbies often start using a Linux system guided by some manual or |
| 48 |
other piece of literature that may, or may not, be Debian-specific. Many |
| 49 |
introductory Linux books describe/demonstrate the same utilities and |
| 50 |
programs; however several of these examples don't have much to do with the |
| 51 |
daily routine of a more experienced user. |
| 52 |
|
| 53 |
What they do use: |
| 54 |
- install tools |
| 55 |
- "easy" packages, like task-newbie-help, task-dialup(-isdn), X, Gnome |
| 56 |
|
| 57 |
What they don't use: |
| 58 |
- "difficult to learn" packages, like task-sgml, task-fortran |
| 59 |
- development packages (well, they may want to compile a new kernel) |
| 60 |
|
| 61 |
ad b. When comparing Linux distributions, quite often either a simple |
| 62 |
install without much packages is tried, to see "what it looks like", or a |
| 63 |
more elaborate install that mimics one's currently working system, to find |
| 64 |
out "what it feels like." Once Debian is recognized as the truly best |
| 65 |
distribution, a complete CD set will be bought which will be used to |
| 66 |
set-up the production system(s). |
| 67 |
|
| 68 |
What they do use: |
| 69 |
- install tools |
| 70 |
- "easy" packages |
| 71 |
- to compare distributions: packages found in their current distribution / |
| 72 |
other distributions from which they have collected CDs |
| 73 |
|
| 74 |
What they don't use: |
| 75 |
- packages that require much setup/tuning, or just "a long time to get |
| 76 |
functional", like task-database-*, task-news-server, |
| 77 |
task-parallel-computing-node |
| 78 |
- "heavy development" packages, like task-sgml-dev, task-objc-dev |
| 79 |
(maybe they are interested in these packages, but they will recognize |
| 80 |
them as being "advanced", and not expect them on the "most popular" CD) |
| 81 |
|
| 82 |
ad c. Upgrading as much packages as possible from a single CD means that |
| 83 |
the most-used packages on Debian systems should be present on that CD. |
| 84 |
|
| 85 |
What they do use: |
| 86 |
- packages used on at least 5% of all Debian systems (which happens to be |
| 87 |
the top 5% of the Popularity Contest results) |
| 88 |
|
| 89 |
What they don't use: |
| 90 |
- the rest |
| 91 |
|
| 92 |
Keeping all this in mind, a solution was developed that (implicitly) uses |
| 93 |
all mentioned "rating methods" to create a CD 1 that should answer the |
| 94 |
stated demands as well as possible. The lists were entered, tested, verified, |
| 95 |
cross-checked and adjusted, until an acceptable result was reached. |
| 96 |
|
| 97 |
|
| 98 |
Further work/Recommendations: |
| 99 |
|
| 100 |
The described procedure has resulted in a drastically reduced number of |
| 101 |
task-* packages that are forced to go on the first CD. But since the |
| 102 |
Popularity Contest can't handle task-* packages very well, most of them |
| 103 |
will be moved to the last CD in the set, while in many cases all of their |
| 104 |
"contents" are available on "more popular" CDs. It would make more sense |
| 105 |
if a task package is included as soon as, say, 50-70% of it's dependencies |
| 106 |
are included. Since all APT tools are available during CD image creation, |
| 107 |
this can probably be automated entirely. |