among the recent action for python2 genocide on TW, asciidoc is also its target. Unfortunately, there are still lots of packages that rely on asciidoc for generating man pages and documents, hence simply dropping it shall result in many build breakage.
Now my question is what action we should take.
A: Drop asciidoc package now and let each package maintainer fixing each broken one.
B: Find an alternative, python3 variant of asciidoc (likely a downstream one).
C: Replace with asciidoctor. I've tested with a hackish bash script to make it more compatible with asciidoc.
D: Any other option?
For B and C, we need completely new packages.
I have no idea about option B, so someone else needs to take care of it.
The option C is tested in OBS home:tiwai:test:asciidoc-drop project, which contain two new packages, asciidoc-compat and rubygem-asciidoctor-docbook45. This solution would be on TW only if someone else takes over the maintenance of those two. I have no gut for maintaining them for TW.
And, note that C would still result in lots of formatting issues because of subtle differences between asciidoc and asciidoctor (e.g. inapplicable config snippet, different syntax handling). Also a couple of packages still have some build issues wrt asciidoctor, so they need fixes in addition to a wrapper script.
Last but not least, asciidoctor isn't included in the standard Leap 15.x releases, so unconditionally applying asciidoctor would break the builds in devel projects.
So, please speak up for what way we should go. If anyone is willing to take over the maintenance (either new ones or old one), I'd be really happy, too.