Bug#799792: libtext-multimarkdown-perl: Coexistence with upstream MultiMarkdown-4?

[Guillem Jover]

Package: libtext-multimarkdown-perl
Version: 1.000035-1
Severity: wishlist
Control: block 659343 by -1

Hi!

I've been looking into packaging the latest upstream multimarkdown (ITP
#659343), but one problem I'm facing is that libtext-multimarkdown-perl
provides a /usr/bin/multimarkdown with a somewhat incompatible
command-line interface.

AFAIU the perl module is a fork of the older MultiMarkdown-2 version.
So they are not completely unrelated.

I guess the very basics are "compatible": --help, --version, and FILE.
But the new one does not support --html4tags nor --shortversion. And
in principle the MultiMarkdown-4 syntax should be a superset of the
MultiMarkdown-2.

So I'd like to discuss how could we make these two coexist in the
archive and on installed systems?

I guess some options could be:

1) Name both binaries with the upstream multimarkdown major impl version:
   - Rename perl impl to /usr/bin/multimarkdown-2 (although the fork
     version is 1.x, but was derived from MultiMarkdown-2).
   - Ship C impl as /usr/bin/multimarkdown-4.
1.1) No one claims /usr/bin/multimarkdown. Would probably break stuff.
1.2) Make /usr/bin/multimarkdown an alternatives to distinguish between
     the two. The problem is that they do not provide diverging
     command-line options and syntax support.

2) Make them Conflict/Provides/Replaces multimarkdown.
2.1) Keep the perl binary with the module. This is probably a very bad
     idea because other programs might depend on the perl module.
2.1) Split the perl multimarkdown binary into its own package. It would
     still be bad because of the divering interfaces, and because it
     disallows using both on the same system.

3) Make the MultiMarkdown-4 impl the new one.
   - Leave the perl impl as /usr/bin/multimarkdown.
   - Ship the C impl as /usr/bin/multimarkdown-4.

4) Make the MultiMarkdown-4 impl the canonical one.
   - Rename the perl impl as /usr/bin/multimarkdown-2.
   - Ship the C impl as /usr/bin/multimarkdown.

Or perhaps there are other possible options you see?

I guess this all comes down to the possible cost of a transition,
and/or the benefit of having the latest upstream spec implementation
available for use with the canonical name.

Thanks,
Guillem