From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'brian m. carlson'" <sandals@crustytoothpaste.net>
Cc: "'Bagas Sanjaya'" <bagasdotme@gmail.com>,
"'Git Users'" <git@vger.kernel.org>
Subject: RE: [RFC suggestion] Generate manpage directly with Asciidoctor
Date: Fri, 7 May 2021 21:42:46 -0400 [thread overview]
Message-ID: <013c01d743ab$7577c0d0$60674270$@nexbridge.com> (raw)
In-Reply-To: <YJXF3oq4n/NFJSx3@camp.crustytoothpaste.net>
On May 7, 2021 6:58 PM, brian m. carlson wrote:
>Subject: Re: [RFC suggestion] Generate manpage directly with Asciidoctor
>
>On 2021-05-07 at 12:02:13, Randall S. Becker wrote:
>> On May 7, 2021 2:07 AM, Bagas Sanjaya wrote:
>> >To: Git Users <git@vger.kernel.org>
>> >Subject: [RFC suggestion] Generate manpage directly with Asciidoctor
>> >Asciidoctor has support for directly generating manpage, see [1].
>> >
>> >We support using Asciidoctor as drop-in replacement for original
>> >Asciidoc, but currently we need to use xmlto together with
>> >Asciidoc(tor) to produce manpages. However, most users don't inclined
>> >to install xmlto toolchain, partly because they had to download more
>> >than 300 MB of data just to install xmlto and its dependencies (including
>dblatex and texlive).
>> >
>> >So completely migrating to Asciidoctor can eliminate xmlto
>> >requirement for generating manpage.
>> >
>> >What do you think about above?
>>
>> Our toolchain does not support asciidoctor itself because of porting issues. I
>am not sure it is available everywhere.
>
>I think Asciidoctor is pure Ruby, since it also uses JRuby and Opal to run in Java
>and JavaScript environments. Ruby is relatively portable to most architectures
>and systems (for example, it runs on 16 Debian architectures).
>
>Is the problem in your case Ruby or is it Asciidoctor itself? I'm happy to send
>portability patches to Asciidoctor if necessary, but I'm not sure I'm a good
>candidate to send patches to Ruby itself, especially for an OS I don't use.
In this case, Ruby is not 100% portable to all platforms. I have an old port, but the latest version is not portable because of unportable dependencies - not for a lack of a large amount of trying. So the assumption is not entirely workable. My only option is to take the pre-generated pages from the manpages repo.
-Randall
next prev parent reply other threads:[~2021-05-08 1:42 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 6:06 [RFC suggestion] Generate manpage directly with Asciidoctor Bagas Sanjaya
2021-05-07 12:02 ` Randall S. Becker
2021-05-07 22:55 ` Felipe Contreras
2021-05-07 22:57 ` brian m. carlson
2021-05-08 1:42 ` Randall S. Becker [this message]
2021-05-07 12:27 ` Đoàn Trần Công Danh
2021-05-07 12:47 ` Bagas Sanjaya
2021-05-07 23:03 ` Felipe Contreras
2021-05-08 4:27 ` Bagas Sanjaya
2021-05-07 20:25 ` brian m. carlson
2021-05-07 22:19 ` Jeff King
2021-05-08 4:22 ` Bagas Sanjaya
2021-05-09 8:20 ` Martin Ågren
2021-05-09 18:46 ` Felipe Contreras
2021-05-10 18:43 ` Martin Ågren
2021-05-10 22:24 ` Jeff King
2021-05-11 4:27 ` Felipe Contreras
2021-05-11 6:13 ` Jeff King
2021-05-11 8:03 ` Felipe Contreras
2021-05-11 12:44 ` Ævar Arnfjörð Bjarmason
2021-05-11 19:00 ` Felipe Contreras
2021-05-11 19:09 ` Jeff King
2021-05-11 20:22 ` Felipe Contreras
2021-05-11 23:14 ` brian m. carlson
2021-05-12 1:44 ` Felipe Contreras
2021-05-11 18:45 ` Martin Ågren
2021-05-11 19:07 ` Jeff King
2021-05-11 19:11 ` Martin Ågren
2021-05-11 20:14 ` Felipe Contreras
2021-05-11 9:04 ` Jean-Noël Avila
2021-05-11 18:54 ` Martin Ågren
2021-05-07 23:35 ` Felipe Contreras
2021-05-07 23:57 ` brian m. carlson
2021-05-08 3:10 ` Jeff King
2021-05-08 3:23 ` Jeff King
2021-05-09 0:22 ` brian m. carlson
2021-05-09 8:29 ` Martin Ågren
2021-05-07 22:48 ` Felipe Contreras
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='013c01d743ab$7577c0d0$60674270$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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.