Queries on varieties of update

Asked by Arnab

Hi All,
There are some question regarding downloading the app

1)While downloading the app, is it possible to differentiate among the different OS versions, like OS X 10.5.4 and 10.5.5. Consider the scenario like the updated App version should get downloaded to OS X 10.5.4 not on 10.5.5.

2)While downloading the app, is it possible to differentiate the different versions of Mac, like MacBook Pro and MacBook Air for example in this case the OS version may be same. Consider the scenario like the updated App version should get downloaded to Air not on Pro.

3)Lastly is it going to be possible to differentiate 3rd party application versions also.
Consider the scenario, I have developed an Application on Safari.Now during the time of update is it possible to identify that if the Safari version is this then only the update should happen else not.

Sorry for such long questions.If you get time please reply.
Thanks in advance
Arnab

Question information

Language:
English Edit question
Status:
Solved
For:
Sparkle Edit question
Assignee:
No assignee Edit question
Solved by:
Andy Matuschak
Solved:
Last query:
Last reply:

This question was reopened

Revision history for this message
Andy Matuschak (andymatuschak) said :
#1

1. See the bottom of http://sparkle.andymatuschak.org/documentation/pmwiki.php/Documentation/PublishingAnUpdate

2. No. You can do this yourself though by implementing the delegate method:
- (SUAppcastItem *)bestValidUpdateInAppcast:(SUAppcast *)appcast forUpdater:(SUUpdater *)bundle; (see SUUpdater.h)

3. See #2. Return nil if no update is valid.

Revision history for this message
Arnab (aganguly01) said :
#2

Some pointers for how do I detect the 3rd party application versions, like for example the installation should be valid only when my application uses Safari 3.3 not on Safari 3.2 .

Thanks in advance
Arnab

Revision history for this message
Andy Matuschak (andymatuschak) said :
#3

Sorry, but that really doesn't fall under my purview of support. Check the docs for NSBundle.

Revision history for this message
Arnab (aganguly01) said :
#4

OS version comparison need to be validate:
I referred to the bottom of http://sparkle.andymatuschak.org/documentation/pmwiki.php/Documentation/PublishingAnUpdate

So in my appcast.xml if I put sparkle:minimumSystemVersion "10.6.5" then the update won't happen in 10.5.5 ?But the behavior what I see is not happening in that way.It gets update as well in 10.5.5.Is there any source change is required for the same?
Do I need to do any additional checks.

Secondly Can I modify the log statements like for example when the update is already done and if I forcibly try to update it should say the "application is up to date" also when the OS version mismatch is there it should say similar statments.

Thanks in advance
Arnab

Revision history for this message
Arnab (aganguly01) said :
#5

OS version comparison need to be validate:
I referred to the bottom of http://sparkle.andymatuschak.org/documentation/pmwiki.php/Documentation/PublishingAnUpdate

So in my appcast.xml if I put sparkle:minimumSystemVersion "10.6.5" then the update won't happen in 10.5.5 ?But the behavior what I see is not happening in that way.It gets update as well in 10.5.5.Is there any source change is required for the same?
Do I need to do any additional checks.

Secondly Can I modify the log statements like for example when the update is already done and if I forcibly try to update it should say the "application is up to date" also when the OS version mismatch is there it should say similar statments.

Thanks in advance
Arnab

Revision history for this message
Arnab (aganguly01) said :
#6

OS version comparison need to be validate:
I referred to the bottom of http://sparkle.andymatuschak.org/documentation/pmwiki.php/Documentation/PublishingAnUpdate

So in my appcast.xml if I put sparkle:minimumSystemVersion "10.6.5" then the update won't happen in 10.5.5 ?But the behavior what I see is not happening in that way.It gets update as well in 10.5.5.Is there any source change is required for the same?
Do I need to do any additional checks.

Secondly Can I modify the log statements like for example when the update is already done and if I forcibly try to update it should say the "application is up to date" also when the OS version mismatch is there it should say similar statments.

Thanks in advance
Arnab

Revision history for this message
Andy Matuschak (andymatuschak) said :
#7

Post the URL of your appcast here; I'll take a look.

You can't modify Sparkle's responses without changing the strings files, but it already does what you ask.

Revision history for this message
Arnab (aganguly01) said :
#8

Hi,
Below is the appcast file.
I have kept the sparkle:minimumSystemVersion="10.6.6" but my OS is of 10.5.5.So I am expecting update should fail once I try to download the file from my app.But it gets downloaded and the app gets launched as well.

<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:sparkle="http://www.andymatuschak.org/xml-namespaces/sparkle" xmlns:dc="http://purl.org/dc/elements/1.1/">
   <channel>
      <title>Test App Changelog</title>
      <link>http://10.146.163.102/~bdcuser/appcast.xml</link>
      <description>Most recent changes with links to updates.</description>
      <language>en</language>
         <item>
            <title>Version 2.0 (2 bugs fixed; 3 new features)</title>
      <sparkle:releaseNotesLink>
       http://10.146.163.102/~bdcuser/rnotes.html
      </sparkle:releaseNotesLink>
            <pubDate>Wed, 03 Dec 2008 11:20:11 +0000</pubDate>
            <enclosure url="http://10.146.163.102/~bdcuser/TestApp_2.0.zip" sparkle:version="2.0" sparkle:minimumSystemVersion="10.6.6" length="428416" type="application/octet-stream"/>
         </item>
   </channel>
</rss>

Revision history for this message
Best Andy Matuschak (andymatuschak) said :
#9

Oh ho! That's because there's mistake in the documentation. sparkle:minimumSystemVerrsion is supposed to be a child of <item> (like the release notes link), not an attribute on the <enclosure>. I'll go fix the docs.

Revision history for this message
Arnab (aganguly01) said :
#10

Thanks for the fix and updates.
Arnab