Triode;425879 Wrote: > Right - I never use PluginBuilder... The UUID for the plugin is never > used by SC, so I don't include this. > > I was thinking we could create the install.xml from the repo when you > download it, need to think a bit more about this.
My current publishing procedure (which is a bit more complex than needed) involves the following steps: 1. Update install.xml with the new version number 2. Build the plugin zip using PluginBuilder (a patched version since the official doesn't work with all file extensions) 3. Upload the plugin zip to my public download page 4. Add a description of the changes to my public download page 5. Calculate a new sha checksum for the repository file 6. Edit the repository xml file and change: - <plugin> element with the new plugin version number - <url> element with the new plugin download url - <changes> element which describes the changes in this version - <sha> element with the new sha checksum 7. Upload the repository file to a web server (not the official place) 8. Verify that it works in Extension Downloader by downloading and installing to my local development SqueezeCenter that points to the non official published repository xml file 9. Upload/commit the repository xml file to Google Code to it official location 10. Announce the new version by mailing the description of the changes to a Google Code mailing list 11. Announce the new version by posting the description of the changes to a thread in the SlimDevices forum in the 3rd party plugin section. 12. Install it through Extension Downloader in my own living room setup which points to the official Google Code repository xml. I know this is a bit more complicated that it needed and most plugin developers probably have simpler publication procedure but it felt like a good idea to post my procedure here in case it gives someone some ideas. I currently post the information about changes in the new version in four places (my download page, repository xml, forum and mailinglist), this is something which I would like to simplify so I only put this in the repository xml file. To do that there has to be some way to find latest updates to third party plugins, even those not installed. If we don't want to put this kind of logic into Extension Downloader, it would probably be possible to build a web site around the repository xml files linked from the wiki. Unfortunately changes on many plugins are not posted in the repository xml files at all, so it's a bit hard to do it at the moment. The repository xml file also only contains the changes in the latest version, so it's not possible to see the complete change history. Of course, the typical user probably doesn't care about the change history, they just install a new version when it's available independent what changes it includes. -- erland Erland Isaksson 'My homepage' (http://erland.isaksson.info) (Install my plugins through Extension Downloader) (Developer of 'TrackStat, SQLPlayList, DynamicPlayList, Custom Browse, Custom Scan, Custom Skip, Multi Library, Title Switcher and Database Query plugins' (http://wiki.erland.isaksson.info/index.php/Category:SlimServer)) ------------------------------------------------------------------------ erland's Profile: http://forums.slimdevices.com/member.php?userid=3124 View this thread: http://forums.slimdevices.com/showthread.php?t=63623 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
