From: "Michael Kerrisk" <mtk-manpages@gmx.net>
To: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
Cc: linux-kernel@vger.kernel.org, Rob Landley <rob@landley.net>
Subject: Re: man-pages-2.59 and man-pages-2.60 are released
Date: Thu, 28 Jun 2007 18:17:20 +0200 [thread overview]
Message-ID: <20070628161720.298550@gmx.net> (raw)
In-Reply-To: <4683BC76.8070805@ums.usu.ru>
Alexander,
> > 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.
> 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.)
Cheers,
Michael
--
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7
Want to help with man page maintenance?
Grab the latest tarball at
http://www.kernel.org/pub/linux/docs/manpages ,
read the HOWTOHELP file and grep the source
files for 'FIXME'.
next prev parent reply other threads:[~2007-06-28 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 9:50 man-pages-2.59 and man-pages-2.60 are released Michael Kerrisk
2007-06-26 13:34 ` Rob Landley
2007-06-28 13:49 ` Alexander E. Patrakov
2007-06-28 16:17 ` Michael Kerrisk [this message]
2007-06-28 16:33 ` Alexander E. Patrakov
2007-06-28 16:54 ` Michael Kerrisk
2007-06-28 22:52 ` Bill Davidsen
2007-06-29 8:30 ` Michael Kerrisk
2007-06-29 8:55 ` Alexander E. Patrakov
2007-06-29 9:36 ` Michael Kerrisk
2007-06-29 9:56 ` Alexander E. Patrakov
2007-06-29 14:33 ` Rob Landley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070628161720.298550@gmx.net \
--to=mtk-manpages@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=patrakov@ums.usu.ru \
--cc=rob@landley.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox