Re: [PATCH liburing 0/3] Convert manpages to markdown

Gabriel Krisman Bertazi <[email protected]> writes:

> Jeff Moyer <[email protected]> writes:
>
>> Hi, Gabriel,
>>
>> Gabriel Krisman Bertazi <[email protected]> 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