This is a known issue with no useful response from the upstream maintainer: https://github.com/walles/moar/issues/143
IMO, MacPorts should either make the choice to change the `moar` pager binary to `moar-pager` or set up a conflicting package rule. As I was looking for examples of this, I noticed that the moreutils port excludes its version of parallel, which is easier to use in simple cases than GNU parallel — so that's somewhat disappointing. Maybe we can bring that back as a variant (moreutils+parallel) or a separate port (moreutils-parallel). -a On Mon, Oct 16, 2023 at 8:21 PM Kenneth Wolcott <kennethwolc...@gmail.com> wrote: > Hi; > > Since I have already installed raku I cannot install moar because moar > conflicts with moarvm required by Raku. > > Looks like "moar" (which is better than "less") needs to be renamed > somehow or internally there is a conflict. Trimmed error output is > enclosed below. > > Thanks, > Ken Wolcott > > ............. > Error: Failed to activate moar: Image error: /opt/local/bin/moar is > being used by the active MoarVM port. Please deactivate this port > first, or use 'port -f activate moar' to force the activation. > while executing > "throw registry::image-error $msg" > ("foreach" body line 47) > invoked from within > "foreach file $imagefiles { > set srcfile "${extracted_dir}${file}" > > # To be able to install links, we test if we can lst..." > invoked from within > "registry::write { > foreach file $imagefiles { > set srcfile "${extracted_dir}${file}" > > # To be able to instal..." > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_moar/moar/main.log > for details. > -- Austin Ziegler • halosta...@gmail.com • aus...@halostatue.ca http://www.halostatue.ca/ • http://twitter.com/halostatue