[opensuse-packaging] Dropping asciidoc on TW (or other possible solutions)
Hi, 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. thanks, Takashi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 2020-01-13 14:07, Takashi Iwai wrote:
B: Find an alternative, python3 variant of asciidoc (likely a downstream one).
Is this in your radar? https://github.com/asciidoc/asciidoc-py3 Looks like that have the same dependencies. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi, On 13 Jan 14:07, Takashi Iwai wrote:
Hi,
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?
There is also https://asciidoc3.org/ Regards, ismail -- 1 + 1 = 1 for very large values of 1 SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany GF: Felix Imendörffer (HRB 36809, AG Nürnberg)
On Mon, 13 Jan 2020 14:13:59 +0100, İsmail Dönmez wrote:
Hi,
On 13 Jan 14:07, Takashi Iwai wrote:
Hi,
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?
There is also https://asciidoc3.org/
It's meant as option B. thanks, Takashi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Mon, Jan 13, 2020 at 8:21 AM Takashi Iwai <tiwai@suse.de> wrote:
On Mon, 13 Jan 2020 14:13:59 +0100, İsmail Dönmez wrote:
Hi,
On 13 Jan 14:07, Takashi Iwai wrote:
Hi,
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?
There is also https://asciidoc3.org/
It's meant as option B.
The asciidoc community officially has a Python 3 port with asciidoc-py3. Fedora's asciidoc package already switched to it some time ago. -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Mon, 13 Jan 2020 14:22:21 +0100, Neal Gompa wrote:
On Mon, Jan 13, 2020 at 8:21 AM Takashi Iwai <tiwai@suse.de> wrote:
On Mon, 13 Jan 2020 14:13:59 +0100, İsmail Dönmez wrote:
Hi,
On 13 Jan 14:07, Takashi Iwai wrote:
Hi,
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?
There is also https://asciidoc3.org/
It's meant as option B.
The asciidoc community officially has a Python 3 port with asciidoc-py3. Fedora's asciidoc package already switched to it some time ago.
Oh that's a good news. Then I'll just wait for the taker of the new package :) thanks, Takashi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Mon, 13 Jan 2020 14:26:39 +0100, Takashi Iwai wrote:
On Mon, 13 Jan 2020 14:22:21 +0100, Neal Gompa wrote:
On Mon, Jan 13, 2020 at 8:21 AM Takashi Iwai <tiwai@suse.de> wrote:
On Mon, 13 Jan 2020 14:13:59 +0100, İsmail Dönmez wrote:
Hi,
On 13 Jan 14:07, Takashi Iwai wrote:
Hi,
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?
There is also https://asciidoc3.org/
It's meant as option B.
The asciidoc community officially has a Python 3 port with asciidoc-py3. Fedora's asciidoc package already switched to it some time ago.
Oh that's a good news. Then I'll just wait for the taker of the new package :)
And Martin merged the change (again) without the ack of the package maintainer. Too bad, really. The py3 version should be rather a new package. It can obsolete the py2 version. I revert it now. Martin, if you want to go for this change, just create a new package and become its maintainer, then submit to Factory. thanks, Takashi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (4)
-
aplanas -
İsmail Dönmez -
Neal Gompa -
Takashi Iwai