maximumSystemVersion key

Bug #449942 reported by Jeremy Huddleston on 2009-10-12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fix Committed

Bug Description

This bug report follows from

Essentially, there needs to be functionality in place to set a maximum system OS version for a package rather than just minimum.

Jeremy Huddleston (jeremyhu) wrote :

This is actually quite important now:

SnowLeopard users are being given Leopard versions to install! I know I can't do anything about current releases, but I'd like this fixed before my next release, so the following update goes smoothly.



koda (vitto-giova) wrote :

i'd like to have this feature as well.
In this way we could issue 64bit bundles to Snow Leopard users and 32bit ones to Tiger and Leopard users.
Is there any update?

Andy Matuschak (andymatuschak) wrote :

Sorry, no update. If anyone can contribute a patch to resolve this, I'd be happy to apply it, but I'm unlikely to have time to write one myself anytime soon.

Changed in sparkle:
status: New → Confirmed
importance: Undecided → Medium
Jeremy Huddleston (jeremyhu) wrote :

I don't have the time to work on it either since our workaround is "good enough" for now:

1) using min-required of 10.6 (even though it is really 10.6.3) for SL versions
2) Releasing the SL version with a bundle version +1 over the Leopard version

You also have to make sure the timestamps are ordered correctly.

H0ff1 (stefhoff) on 2012-05-28
Changed in sparkle:
assignee: nobody → H0ff1 (stefhoff)
H0ff1 (stefhoff) on 2012-05-29
Changed in sparkle:
status: Confirmed → In Progress
H0ff1 (stefhoff) on 2012-06-09
Changed in sparkle:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions