From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Jeff Moyer <jmoyer@redhat.com>
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 11:20:07 -0400 [thread overview]
Message-ID: <87y0fmhlnc.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <x49fr1vvvbe.fsf@segfault.usersys.redhat.com>
Jeff Moyer <jmoyer@redhat.com> writes:
> 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.
Oh, that is a bummer!
> 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.
I suppose we'll have to keep them in-tree, no way around that.
RHEL is unlikely to be the only problematic distro.
The question is whether we want to do the md conversion at all and have
both in-tree or just drop this entirely. On the bright side, Markdown
is much easier to write, but duplicating the sources can make them go
out of sync.
> At the very least, please make generation of the man pages optional
> via configure.
> Thanks!
> Jeff
>
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2026-07-07 15:20 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 ` [PATCH liburing 0/3] " Jeff Moyer
2026-07-07 14:56 ` Jeff Moyer
2026-07-07 15:20 ` Gabriel Krisman Bertazi [this message]
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=87y0fmhlnc.fsf@mailhost.krisman.be \
--to=krisman@suse.de \
--cc=ammarfaizi2@gnuweeb.org \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=jmoyer@redhat.com \
/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.