Alexander,Why? I'm not questioning the policy, it's just that if HUGE kernel versions are kept available forever, a tiny man page tar would not seem to be a disk space issue.
I just released man-pages-2.59 and man-pages-2.60.
These releases are now available for download at:
http://www.kernel.org/pub/linux/docs/manpages
Yes, just this morning I decided to tidy away some of the old
tarballs into a newly created "old" directory.
There is one little problem with this: there is no stable URL for a given version.
Well, there never really was. To date, most old tarballs have
had only a limited life on kernel.org.
Why not just a link with a fixed name (LATEST?) which could be updated? I assume installing a new version is automated to create and install the tar, any needed links, the push to mirrors, etc. So it would just be a single step added to an automated procedure. You could have a link in "Old" as requested, and any other links as well.This hurts, e.g., automated Linux From Scratch rebuilds (the official script grabs the URL from the book, but it becomes invalid too
soon).
Could you please, in order to avoid this, do what SAMBA team does: place into http://www.kernel.org/pub/linux/docs/manpages/Old not only old versions, but also the current version? This way, LFS will be sure that
the 2.60 version is always available as
As noted above old versions never were "always available" on
kernel.org...
http://www.kernel.org/pub/linux/docs/manpages/Old/man-pages-2.60.tar.bz2 (even if it is in fact the latest version).
How about a link in /pub/linux/docs/manpages/ of the form "LATEST-IS-m.xy"? Rob Landley was wanting something like this,
and I guess it would be easy for LFS to build a simple
script that looks for that link and deduces "man-pages-m.xy" from it. (I've just now created such a link in the directory,
as an example.)