Homebrew Disables OSXFuse ports

[Mark Anderson]

I agree with Perry, partly because the developer seems combative and I
worry what happens if he decides to stop working on it one day.

But I also don't want to remove all the ports - this kinda leads into why I
want cask like functionality, but then again, who would notice if they just
wanted to install ssh-fuse or something.

My other issue is we have two ports - which I think Ryan indicated is kinda
confusing/bad. That one seems easiest to fix.

—Mark
_______________________
Mark E. Anderson <mark at macports.org>
MacPorts Trac WikiPage <https://trac.macports.org/wiki/mark>
GitHub Profile <https://github.com/markemer>



On Mon, May 17, 2021 at 7:06 PM Ryan Schmidt <ryandesign at macports.org>
wrote:

> On May 17, 2021, at 08:44, Perry E. Metzger wrote:
>
> > On 5/17/21 01:44, Ryan Schmidt wrote:
> >> On May 16, 2021, at 21:49, Mark Anderson wrote:
> >>
> >>> Given some of our recent back and forth, I found this interesting:
> https://github.com/Homebrew/homebrew-core/pull/74812
> >> Meh. They have different priorities than we do. No reason for us to
> follow what they do.
> >
> > In this instance, though, I think their reasoning is correct.
>
> So you would like MacPorts to delete all ports that depend on osxfuse, and
> all ports that depend on those ports, and so on?
>
> Each of those ports was added to MacPorts because someone wanted it. What
> are they to do once we delete them?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20210517/f4e7ce71/attachment.htm>