Re: Homebrew Disables OSXFuse ports

[Ryan Schmidt]

On May 17, 2021, at 21:00, Perry E. Metzger wrote:

> On 5/17/21 19:06, Ryan Schmidt wrote
 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?
> 
> The FUSE implementation itself already has a binary installer (and indeed, we 
> cannot build it from source since there are none), and so if one wants it, 
> it's easy to install without our infrastructure.

As I said there are many ports in MacPorts that depend on fuse. Thus, we must 
offer fuse as a port in MacPorts if we want to continue to have those ports. 
MacPorts ports are not, as a rule, supposed to require the user to install 
other things outside of MacPorts.


> I've suggested elsewhere that it's a good idea to probably take the last open 
> source version of FUSE for MacOS and figure out how to get it to work without 
> needing a kernel extension given that those are on the way out.

If someone is interested in forking osxfuse/macfuse or any other software to 
improve it in a different direction from the original developer, that's their 
prerogative.

Re: Homebrew Disables OSXFuse ports

[Perry E. Metzger]

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.


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.


Perry

On 5/17/21 20:27, Mark Anderson wrote:
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 
MacPorts Trac WikiPage 
GitHub Profile 



On Mon, May 17, 2021 at 7:06 PM Ryan Schmidt  
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?

Re: Homebrew Disables OSXFuse ports

[Perry E. Metzger]

On 5/17/21 19:06, Ryan Schmidt wrote

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?


The FUSE implementation itself already has a binary installer (and 
indeed, we cannot build it from source since there are none), and so if 
one wants it, it's easy to install without our infrastructure.


I've suggested elsewhere that it's a good idea to probably take the last 
open source version of FUSE for MacOS and figure out how to get it to 
work without needing a kernel extension given that those are on the way out.


Anyway, this is just one person's opinion. I'm not going to yell very 
loud if it stays, but it feels icky to me.


Perry

Re: Homebrew Disables OSXFuse ports

[Ruben Di Battista]

I personally feel that the developer has the right of having their own
opinion, and rightly so. Lots of commercial software do not contribute back
to the foundation made by open source projects and the fact that it is
taken for granted that someone is working free on such important piece of
software makes me uncomfortable.

If the developer decides to stop working on the code, and the code stops
working on some machines, then maybe deleting the package has a reason.

At this point, I think Macports should keep shipping osxfuse and related
ports in binary form. But we already faced this discussion... 


On Tue, 18 May 2021, 02:27 Mark Anderson,  wrote:

> 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 
> MacPorts Trac WikiPage 
> GitHub Profile 
>
>
>
> On Mon, May 17, 2021 at 7:06 PM Ryan Schmidt 
> 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?
>>
>>

Re: 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 
MacPorts Trac WikiPage 
GitHub Profile 



On Mon, May 17, 2021 at 7:06 PM Ryan Schmidt 
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?
>
>

Re: Homebrew Disables OSXFuse ports

[Ryan Schmidt]

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?

Re: Homebrew Disables OSXFuse ports

[Perry E. Metzger]

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.

Re: Homebrew Disables OSXFuse ports

[Perry E. Metzger]

They seem to share my opinion.

On 5/16/21 22:49, Mark Anderson wrote:
Given some of our recent back and forth, I found this interesting:Â 
https://github.com/Homebrew/homebrew-core/pull/74812

Re: Homebrew Disables OSXFuse ports

[Andrew Janke]

On 5/17/21 1:44 AM, 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.
>

+1 to this. I'm a sometimes user of some of these OSXFuse-using
projects, and would like to see them continue to be supported in some
package manager.

Cheers,
Andrew

Re: Homebrew Disables OSXFuse ports

[Eric Gallager via macports-dev]

I like having Fuse ports available in MacPorts, I just wish they
didn't break as often; see the following bugs:
https://trac.macports.org/ticket/59316
https://trac.macports.org/ticket/62226

On Mon, May 17, 2021 at 4:55 AM Ruben Di Battista
 wrote:
>
> I also agree with Ryan. Osxfuse is a dependency on some projects that are 
> very useful and shipping it in binary form is very therefore useful too.
>
> On Mon, 17 May 2021, 07: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.
>>

Re: Homebrew Disables OSXFuse ports

[Ruben Di Battista]

I also agree with Ryan. Osxfuse is a dependency on some projects that are
very useful and shipping it in binary form is very therefore useful too.

On Mon, 17 May 2021, 07: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.
>
>

Re: Homebrew Disables OSXFuse ports

[Ryan Schmidt]

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.