multimarkdown, mtools: Resolve mmd conflict

[a2ff]

multimarkdown has a declared conflict with mtools, i suppose due to names of installed files. This is not an adequate solution, as multimarkdown and mtools are in completely different fields and can reasonably be both needed by a user.

A better solution would be to prefix the names of files installed by one or the other (yes this may be a problem for some dependents, whose scripts would have to be adjusted - at least this can be made a macports variant). I submit that multimarkdown is "less" fundamental than mtools and thus is the one that shall have its files prefixed (say, with "mmd-").

[ryandesign (Ryan Carsten Schmidt)]

The conflict isn't "undue". The two ports both want to install a program called mmd. That's a conflict.

Renaming one of the programs to resolve the conflict can be considered. Ideally someone would bring the conflict to the attention of the developers of both software packages so they can weigh in on how they think the conflict should be resolved and ideally implement the resolution themselves in a new version to which we can then update. I'm not planning on starting that conversation myself right now, but please do if you're interested; let us know the results. You could also look at how Debian has solved the problem; my understanding is they have a policy that there shall not be multiple packages that install the same file path so they may already have made a decision on which one to rename which we could follow, assuming they have both packages.

[a2ff]

It is my understanding too, that Debian forbids packages with same filenames (they have "alternatives" for that case, similar to "*-select" MacPorts). Debian does not have multimarkdown related to ​https://github.com/fletcher/MultiMarkdown-6. They have a libtext-multimarkdown-perl that seems unrelated (comes from ​https://metacpan.org/dist/Text-MultiMarkdown).

MTools is a 29-year old project, it reasonably has precedence over the executable name "mmd". Somehow, I suspect the author of multimarkdown is not going to care...

Because the TextMate2 build is broken anyway (see #72944) and has multimarkdown as a mandatory builddep, I'll install MacroMates' binary package instead, for a middle-of-the-road editor between VS Code and MacVim.

Thanks for your time.