`sudo port install moar +pager` should work after an update. On Thu, Nov 30, 2023 at 12:23 AM Kenneth Wolcott <kennethwolc...@gmail.com> wrote:
> AWESOME! > > On Wed, Nov 29, 2023 at 9:13 PM Austin Ziegler <halosta...@gmail.com> > wrote: > > > > Hi, Kenneth. > > > > I finally got around to figuring out how to resolve this[1] and have > opened a > > new PR[2] which, if accepted, will allow you to install moar with the > +pager > > variant, bypassing the mutual conflict on both sides (so you can install > > moar +pager before MoarVM or vice-versa). moar will be called moar-pager > > with the +pager variant, so any configuration you do to $PAGER will need > > to be updated to use moar-pager instead of moar. > > > > riff and ugrep, if used, will be patched to recognize moar-pager in > addition > > to moar as a pager. > > > > -a > > > > [1] https://trac.macports.org/ticket/6849 > > [2] https://github.com/macports/macports-ports/pull/21604 > > > > On Tue, Oct 17, 2023 at 9:16 PM Kenneth Wolcott < > kennethwolc...@gmail.com> wrote: > >> > >> Hi; > >> > >> I noticed today that when trying to build moar port from source that > >> port stops immediately by stating the previously-known conflict with > >> MoarVM rather than building it first and then complaining when the > >> installation occurs and the conflict is readily apparent. This is an > >> improvement; thanks to those who improved this. It would be great to > >> have both co-exist peacefully, however. > >> > >> Thanks, > >> Ken > >> > >> On Mon, Oct 16, 2023 at 6:53 PM Austin Ziegler <halosta...@gmail.com> > wrote: > >> > > >> > 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 > > > > > > > > -- > > Austin Ziegler • halosta...@gmail.com • aus...@halostatue.ca > > http://www.halostatue.ca/ • http://twitter.com/halostatue > -- Austin Ziegler • halosta...@gmail.com • aus...@halostatue.ca http://www.halostatue.ca/ • http://twitter.com/halostatue
