All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Bruce Dubbs <bruce.dubbs@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.37
Date: Wed, 2 Jun 2021 17:27:10 +0200	[thread overview]
Message-ID: <20210602152710.jjs2fpkcegtvlnvb@ws.net.home> (raw)
In-Reply-To: <e00ea8fe-e848-73c1-1314-de26ad698c90@gmail.com>

On Tue, Jun 01, 2021 at 01:29:21PM -0500, Bruce Dubbs wrote:
> On 6/1/21 2:38 AM, Karel Zak wrote:
> > 
> > The util-linux release v2.37 is available at
> > 
> >    http://www.kernel.org/pub/linux/utils/util-linux/v2.37/
> > 
> > Feedback and bug reports, as always, are welcomed.
> > 
> >    Karel
> 
> Karel, Is there any chance you can release a tarball with rendered man
> pages?  It would make things a lot easier for us.

I'm not sure if duplicate content in the upstream source
tarball is a good idea (it means keep there AsciiDoc as well as
generated man pages).

Maybe we can create a separated tarball util-linux-man-2.37.tar.gz and
distribute it by kernel.org FTP for users who do not want to depend on
AsciiDoc. It would be also usable in the future when we will have the
man pages translated to other languages.

The problem is content which depends on the configuration (variables
like $ADJTIME_PATH, $docdir, etc.), because it's distro-specific and
these variables are replaced by real data during conversion from
AsciiDoc,  but I guess this is something we can fix by simple sed call
in the Makekefile.am.

So, your work-flow will be:

 * download and extract source tar.gz
 * download and extract man-pages tar.gz to the same directory as source
 * ./configure [--disable-asciidoc]
 * make
 * make install

Does it sounds usable?

 Karel


-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com


  parent reply	other threads:[~2021-06-02 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01  8:38 [ANNOUNCE] util-linux v2.37 Karel Zak
     [not found] ` <e00ea8fe-e848-73c1-1314-de26ad698c90@gmail.com>
2021-06-02 15:27   ` Karel Zak [this message]
2021-06-02 16:25     ` Bruce Dubbs
2021-06-03 10:19       ` Karel Zak
2021-06-03 17:40         ` Bruce Dubbs
2021-07-22 14:57           ` Karel Zak

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=20210602152710.jjs2fpkcegtvlnvb@ws.net.home \
    --to=kzak@redhat.com \
    --cc=bruce.dubbs@gmail.com \
    --cc=util-linux@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.