Bug 11198 - Extension Downloader: need way to identify newest extension
: Extension Downloader: need way to identify newest extension
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Plugin
: 7.4.0
: PC Other
: -- normal (vote)
: 7.4.0
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-26 04:29 UTC by Peter Watkins
Modified: 2009-10-05 14:38 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Watkins 2009-02-26 04:29:00 UTC
There needs to be some way, preferably in the install.xml file, that a repository can indicate which extension or plugin is most recent. 

I recently updated the script I use to make my install.xml file. Previously it only listed the latest version of each plugin, but as I expect to release some new versions that require a release newer than 7.3.0, I need it to be capable of listing multiple versions. It created an install.xml that had two KitchenTimer entries. One for version "0.7pre3" had a min SC version of 7.2; a later release, version "0.7a22" had a min SC version of 7.0 (yes, my later releases run on a broader range of SC installs). Extension Downloader suggested that I "upgrade" from 0.7a22 to 0.7pre3, which is not correct. I expect that it did so because "0.7pre3" is alphabetically greater than "0.7a22". 

There should be a way of specifying the relative age of different offerings. Most simply, there could be a serialNumber attribute in the XML that would be defined generically as a float number (much like the SOA serial numbers in BIND DNS configurations). Developers would probably simply use the zip file's last modified attribute in seconds-since-Epoch format. Extension Downloader would then only need to numerically compare serialNumber for different versions of an extension with the same name that supported the user's SC version.
Comment 1 Adrian Smith 2009-03-07 08:15:19 UTC
Moved to compare versions using Slim::Utils::Versions in change 25396.  Please verify this works for all cases (my initial checks suggests it is ok for all version numbering currently used)
Comment 2 James Richardson 2009-03-18 11:06:16 UTC
Triode: would this be yours to look at?
Comment 3 Adrian Smith 2009-03-18 11:22:08 UTC
I think its fixed by the move to Slim::Utils::Versions - Peter please reopen if not.
Comment 4 James Richardson 2009-10-05 14:38:06 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.