<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>This is one reasonable compromise, given that a binary installer
exists from the (combative, not very reasonable) developer if one
wants it. One could then just leave the dependent ports and tell
people to install the binary themselves if they want it.</p>
<p>That said, I think it would be a boon to the community to have a
version of FUSE that would work for the long term going forward
and which was open source.<br>
</p>
<p>Perry<br>
</p>
<div class="moz-cite-prefix">On 5/17/21 20:27, Mark Anderson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CACahOHRYVP_9knaWmG6R7O9kTmwGKKueb8S9vu9yy=LV2Xctbw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>My other issue is we have two ports - which I think Ryan
indicated is kinda confusing/bad. That one seems easiest to
fix.</div>
<br clear="all">
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>—Mark<br>
</div>
<div>_______________________<br>
Mark E. Anderson <<a href="mailto:mark@macports.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">mark@macports.org</a>><br>
</div>
<div><a href="https://trac.macports.org/wiki/mark"
target="_blank" moz-do-not-send="true">MacPorts Trac
WikiPage</a><br>
</div>
<div><a href="https://github.com/markemer" target="_blank"
moz-do-not-send="true">GitHub Profile</a><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, May 17, 2021 at 7:06
PM Ryan Schmidt <<a href="mailto:ryandesign@macports.org"
moz-do-not-send="true" class="moz-txt-link-freetext">ryandesign@macports.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On
May 17, 2021, at 08:44, Perry E. Metzger wrote:<br>
<br>
> On 5/17/21 01:44, Ryan Schmidt wrote:<br>
>> On May 16, 2021, at 21:49, Mark Anderson wrote:<br>
>> <br>
>>> Given some of our recent back and forth, I found
this interesting: <a
href="https://github.com/Homebrew/homebrew-core/pull/74812"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/Homebrew/homebrew-core/pull/74812</a><br>
>> Meh. They have different priorities than we do. No
reason for us to follow what they do.<br>
> <br>
> In this instance, though, I think their reasoning is
correct.<br>
<br>
So you would like MacPorts to delete all ports that depend on
osxfuse, and all ports that depend on those ports, and so on?<br>
<br>
Each of those ports was added to MacPorts because someone
wanted it. What are they to do once we delete them?<br>
<br>
</blockquote>
</div>
</blockquote>
</body>
</html>