I don’t actually think that moar is the "more established" project. The MoarVM is the latest iteration of several VMs used during the Perl 6 / Rakudo development cycles which I have followed off and on for going on twenty years. The oldest tag that I could find from the MoarVM was the 2014.1 release when they apparently moved development to GitHub. That does not mean that it was the first release, but perhaps the first "stable" release. I haven’t followed its development that closely, but as a language aficionado I have certainly followed it periodically.

On the other hand, the first I had heard of moar, riff, and urge was yesterday, yesterday, and today (respectively). Not that my not hearing about a project is a sign of anything except that there are a lot of projects out there and it’s really hard to hear about most of them.

If the decision is made to rename the moar binary is made (this is not up to me; there are port maintainers and there is a ticket open which proposes this), we can explore patches to riff and ugrep — although the general preference by most package maintainers is to have such patches applied upstream (that is, riff and ugrep could be modified to look for $PAGER, moar, moar-pager, and less) where possible.

When Google released go, there were complaints about conflicting projects and binaries (including one other software development language, Go!).

Just personally, I would not use the Homebrew analytics data as anything serious, since most Go programs are also installable like go install GitHub.com/walles/moar@latest (and how I install most Go programs, because I don't like Homebrew even as I use it) and it covers a large fraction of macOS users and a very small fraction of Linux users … and pretty much no one else.

Aside from what I have recommended for moar in macports:trac#68491, I think it would be friendlier to your users who also happen to be users of NQP/Rakudo to offer an option of installing moar as moar-pager.

If I have time (doubtful right now), I am going to see if it is possible for MacPorts to declare that a variant does not conflict so that people who use both MoarVM and moar can install them side-by-side with sudo port install MoarVM moar+pager and the moar binary and manpage will be installed as moar-pager, because getting a language ecosystem to move is far more trouble than changing a pager utility and other tools that can take advantage of it out of the box.

Name conflicts with MoarVM #143

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions