public inbox for io-uring@vger.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 14:12:50 -0400	[thread overview]
Message-ID: <x49zf02vfbx.fsf@segfault.usersys.redhat.com> (raw)
In-Reply-To: <87y0fmhlnc.fsf@mailhost.krisman.be> (Gabriel Krisman Bertazi's message of "Tue, 07 Jul 2026 11:20:07 -0400")

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

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

Well, RHEL is often an outlier, but there are derivatives that will
likely also see this issue.

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

I don't have a strong opinion.  Either way, I'll be looking at
documentation and/or prior examples to make the changes I need to make.
:)  As I said in my last follow-up, it would be enough for me if the
generated man pages were simply part of the release tarballs (it's not
necessary to check them into git).  I'm sure that can be accomplished
with makefile magic.

>> At the very least, please make generation of the man pages optional
>> via configure.

And this would be a necessary part of the solution, were things to go
that way.

Thanks!
Jeff


  reply	other threads:[~2026-07-07 18:13 UTC|newest]

Thread overview: 9+ 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
2026-07-07 18:12     ` Jeff Moyer [this message]
2026-07-07 22:05       ` Gabriel Krisman Bertazi

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=x49zf02vfbx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox