public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Michael Kerrisk <mtk-manpages@gmx.net>
Cc: "Alexander E. Patrakov" <patrakov@ums.usu.ru>,
	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:52:11 -0400	[thread overview]
Message-ID: <46843B9B.2080700@tmr.com> (raw)
In-Reply-To: <20070628161720.298550@gmx.net>

Michael Kerrisk wrote:
> 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.
> 
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.

>> 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.)
> 
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.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

  parent reply	other threads:[~2007-06-28 22:50 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
2007-06-28 16:33     ` Alexander E. Patrakov
2007-06-28 16:54       ` Michael Kerrisk
2007-06-28 22:52     ` Bill Davidsen [this message]
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=46843B9B.2080700@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk-manpages@gmx.net \
    --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