public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: Michael Kerrisk <mtk-manpages@gmx.net>
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 22:33:15 +0600	[thread overview]
Message-ID: <4683E2CB.8090100@ums.usu.ru> (raw)
In-Reply-To: <20070628161720.298550@gmx.net>

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

We don't care about the latest version, so the link neither helps nor hurts 
us. What's needed is that the URL and the MD5 sum for a version in the book 
don't change, and that LFS developers have a reasonable time (say, two 
weeks) to react to version updates. We don't want every other SVN commit to 
the book source to be a version update of man-pages :)

E.g., currently, the book at 
http://www.linuxfromscratch.org/lfs/view/development/chapter03/packages.html 
says:

  Man-pages (2.56) - 1,764 KB:
     Download: 
http://www.kernel.org/pub/linux/docs/manpages/man-pages-2.56.tar.bz2
     MD5 sum: 4144874a924b0a8d1f67e19f70d13f08

The script parses this information out of the XML source of the book, 
downloads the package and installs it according to the instructions found 
elsewhere in the book.

The script (jhalfs) and the book can be downloaded from svn:

svn co svn://svn.linuxfromscratch.org/ALFS/jhalfs/trunk jhalfs
svn co svn://svn.linuxfromscratch.org/LFS/trunk/BOOK lfs

-- 
Alexander E. Patrakov

  reply	other threads:[~2007-06-28 16:33 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 [this message]
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=4683E2CB.8090100@ums.usu.ru \
    --to=patrakov@ums.usu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk-manpages@gmx.net \
    --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