I'd actually prefer to have much less than that. We say something like
"if you're using Linux or a Unix installation, such as OpenSolaris,
check with your distributor to see if they already package Django." If
you're using a Linux distro and don't know how to find out if a package
is available, then now is a good time to learn anyway.
Keeping even a list of links to most recent packages up to date is going
to be onerous. There are over 200 Linux distributions. Where do we draw
the line? By favouring nobody special, it's easier.
Then we definitely can have a wiki page of links to the latest packages
and all 200 Linux distros plus Sun plus SCO plus IBM can all update it
We spend a lot of time, unfortunately, doing OS-specific support and it
takes time away from things that are much more in scope for Django. We
can't really avoid doing something special for Mac and Windows, since
their general third-party packaging support is so woeful as to be almost
non-existent. Linux and Unix distros have generally solved that problem,
to the point of providing standard tools to allow package searches and
installs, so let's rely on them as much as we can.
+1. This is something we can very easily defer to the wiki and the community.
There are two parts required here -
1) The wiki needs to be updated, adding an index page for installation
instructions, plus linking to individual pages for the install
instructions for each distro),
2) A first draft of the text to put on the installation instructions page.
This should also be opened as a new ticket, unifying (and deprecating)
the other tickets you mentioned.
Russ Magee %-)