All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: axboe@kernel.dk,  io-uring@vger.kernel.org,  ammarfaizi2@gnuweeb.org
Subject: Re: [PATCH liburing 0/3] Convert manpages to markdown
Date: Tue, 07 Jul 2026 08:27:33 -0400	[thread overview]
Message-ID: <x49fr1vvvbe.fsf@segfault.usersys.redhat.com> (raw)
In-Reply-To: <20260706214132.2841060-1-krisman@suse.de> (Gabriel Krisman Bertazi's message of "Mon, 6 Jul 2026 17:41:22 -0400")

Hi, Gabriel,

Gabriel Krisman Bertazi <krisman@suse.de> writes:

> This obviously adds a build dependency on pandoc, which is already
> packaged by any sane distro out there.  The configure file is updated to
> check for that.

I guess RHEL is not a sane distribution, then.  :)  pandoc was abandoned
in favor of ghc-pandoc, and RHEL does not ship a haskell compiler.  It
would make RHEL packaging considerably easier if the generated man pages
continued to be part of the upstream git tree.  If that's not acceptable,
then I can work around the problem, but it will be a pain.  At the very
least, please make generation of the man pages optional via configure.

Thanks!
Jeff


  parent reply	other threads:[~2026-07-07 12:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 21:41 [PATCH liburing 0/3] Convert manpages to markdown Gabriel Krisman Bertazi
2026-07-06 21:41 ` [PATCH liburing 1/3] man: Generate aliases during compilation Gabriel Krisman Bertazi
2026-07-06 21:41 ` [PATCH liburing 2/3] man: Introduce rules to convert Markdown to groff Gabriel Krisman Bertazi
2026-07-06 21:41 ` [PATCH liburing 3/3] man: Convert manpages to markdown Gabriel Krisman Bertazi
2026-07-07 12:27 ` Jeff Moyer [this message]
2026-07-07 14:56   ` [PATCH liburing 0/3] " Jeff Moyer
2026-07-07 15:20   ` Gabriel Krisman Bertazi
2026-07-07 18:12     ` Jeff Moyer
2026-07-07 22:05       ` Gabriel Krisman Bertazi
2026-07-10 12:14         ` Jeff Moyer

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=x49fr1vvvbe.fsf@segfault.usersys.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=ammarfaizi2@gnuweeb.org \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=krisman@suse.de \
    /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.