Bug#57117: Structure of Release is Confusing

[Ross Boylan <RossBoylan@stanfordalumni.org>]

I do think that in the current structure it is hard to figure out where to
start and what to get, and that the addition of more flavors is likely to
complicate things further.  I have no particular opinion on the merits of
the alternative proposal vs the current setup, or about closing the bug.

I would like to toss in another suggestion, however: why not use links so
that the various flavors all have a complete set of files?
So the top level directory would consist ONLY of a readme and directories.
The readme would outline how to choose which directory (flavor) was
appropriate for you.
The "real" version of the shared files could either go under an appropriate
flavor (perhaps the simplest or the most complex), or into a /shared
subdirectory.

Example Readme:

Each subdirectory here contains a complete installation package.  These in
turn contain subdirectories for different installation media. You should
download the all the files in the subdirectory, along with all those in one
of the media-specific directories under there.  Then you will be ready to
start your install, as described in xxxx.

Most users with standard hardware will find the /compact subdirectory works
for them.  Note the name refers only to the size of the installation files,
not to the size or abilities of the system when installed.

If you have exotic hardware for which you need a driver during installation
(in particular xxx, yyy, or zzz), then use the /full directory.

If you have an xxxx laptop, you will need the /zzz package.

etc.