Suggestion for a new Download page

[Eric Rostetter]

Quoting Raphael Clifford <raphael at clifford.net>:

> I should say straight off that there may be something fundamental about
> yum that I don't understand.  I am getting the impression that you need
> a special version of yum to use fedora-legacy and not just the correct
> yum.conf with any old version of yum. Is this right?

No, it should work with any functioning yum, as long as yum.conf is
set correctly.

> Which I read as a strong advise to give these documents better titles.
> They actually are for people who don't know anything about apt/yum yet
> and provides step-by-step information to them.

Probably true...  No one has suggested a better title yet that I've liked.
Maybe something like "Installing and using yum for Fedora Legacy with Red Hat
Linux 7.2" but that gets kind of long, no?

> rpm.org.  Do you mean there isn't a downloadable yum rpm with yum.conf
> preconfigured for fedora legacy?  There can be documentation for how to

Yes, and hence he can't write complete docs (such as the url to download
from, etc) without the program existing within FL.

> would strongly suggest that any new docs tell people to upgrade rpm to a
> less broken version as the version that comes with redhat 8.0 (at least)
> is truely awful.

We already document that as a suggestion for RH 8/9 (but not RH 7.x).

> I think this is first thing I actually disagree with.  The download
> section should surely help you download whatever you need to download.

It does have links to the FL repository on it.

> For most people that will be yum/apt preconfigured.  A simple line to

For that it points them to the documentation page.

> the effect that "If you are just starting then please go here to get
> everything preconfigured" would do of course on the download page if you

One has been proposed, but I've not had time yet to do anything with it.

> felt that was more appropriate but there should still be links to show
> where to download yum and apt from as well IMHO.

But I'd have to link to each version and constantly update it as we
add/drop versions.  No fun.  There is no single link to all of them,
so this would be a pain.  Instead, they can either use the FL repository
link, or the documentation link.  Until someone comes up with a better
solution.  By better solution, I mean actual description of how to easily
do it and easily maintain it, not just saying "there should be links to
them here..."

--
Eric Rostetter