Opened 10 years ago
Closed 10 years ago
#46525 closed defect (fixed)
osxfuse >=2.7.3 doesn't install on 10.5 (and perhaps later)
Reported by: | fhgwright (Fred Wright) | Owned by: | drkp (Dan Ports) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | Cc: | ||
Port: | osxfuse |
Description
As presently written, the hack to obtain the signed kext from the OSXFUSE release image to get around the Yosemite kext-signing issue always fetches and extracts the .dmg, even when it's not being used. At the very least, this is a waste of time and space, but it also can fail due to incompatibilities in the older tool versions. It's definitely an issue in 10.5; I don't know it it's an issue with any later versions.
The obvious fix (which is a good idea, anyway) is to be more aggressive with the conditionals, and avoid the pointless fetch/extract altogether.
I'm testing an updated Portfile now, so this ticket is just for documentation purposes.
Change History (3)
comment:1 follow-up: 2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | dports@… removed |
---|---|
Owner: | changed from macports-tickets@… to dports@… |
comment:2 Changed 10 years ago by fhgwright (Fred Wright)
Replying to ryandesign@…:
Agreed; I mentioned it a month ago when this change was introduced: https://lists.macosforge.org/pipermail/macports-dev/2014-December/028991.html
I've now determined that installing 2.7.3_1 from source in Snow Leopard Server does *not* fail, so the problem seems to be Leopard-specific. Since Leopard builds were completely broken anyway (due to #45794), I guess this was formerly moot. :-)
Agreed; I mentioned it a month ago when this change was introduced: https://lists.macosforge.org/pipermail/macports-dev/2014-December/028991.html