macfuse

[Ryan Schmidt]

On Dec 25, 2011, at 10:08, Jordan K. Hubbard wrote:

> On Dec 23, 2011, at 1:17 PM, Dan Ports wrote:
> 
>> One argument against removing the port is that fuse4x isn't ABI
>> compatible with MacFUSE. That's hardly an issue for dependent ports, of
>> course, but would break compatibility with non-MacPorts binaries that
>> link against the framework. I'm told that's an issue for some MacFUSE
>> users, although it's not clear how many of them are getting it from
>> MacPorts (or if it's really something we want to support anyway.)
> 
> I can understand the argument, but again, given that MacFuse has been abandoned for almost 5 years now, that seems more like an argument for it to leave macports since it doesn't even compile on anything of recent vintage, and for the folks who are still stuck on PPC (which is also completely deprecated, even as an emulation target), they're likely living off the old precompiled packages from other sources in any case.

I understand that working at a large company such as Apple you have access to the latest and greatest hardware, but not everyone is so lucky. Our standing documented policy is to support the current and previous OS. If maintainers want to support more than that, great. I personally try to accommodate Leopard and Tiger and PowerPC if I can.


> This does, however, open a larger can of worms concerning what the default support footprint of macports should be, and not so much from the perspective of "how many releases back" to go but what the default/supported compilation targets should be.  If it were up to me, and of course it's not, I would declare that all executables should be x86_64 and all libraries/frameworks be i386/x86_64.  Anyone wishing to create binaries for older architectures could simply grab an older release of macports and stick it on an older machine, since any desire to go retro like that is almost certainly driven by the need to create software which is equally retro.

On the contrary: if all you have is an old Mac with an old OS, you might very well want to get newer software onto it, and MacPorts is a great way to do that.


> If macports had binary packages (Internet: "Oh god no not that subject again!")

We have had binary packages (for Snow Leopard x86_64) for months already. We requested a Lion buildbot from Mac OS Forge three months ago in order to make Lion binaries but have received no response to this request.

https://trac.macports.org/ticket/32337