[Sparkle] A Question of Enclosures

[Adam Radestock]

Hi everyone,

I've been rethinking the way SparkleCaster deals with the actual data  
of an update, and thought I'd ask the community for your input on this.
Currently, SparkleCaster requires the developer to drop their zipped,  
tar'd, or DMG'd update package on SparkleCaster's New Version sheet.  
After re-reading Andy's specifications for SparkleCaster, I realised  
that maybe I wasn't doing enough; perhaps I should be asking the  
developer to show me the .app or other bundle, and work the rest out  
for them?
For example, I could take the .app bundle, work out the version number/ 
string and the appcast URL, package the .app in an internet-enabled  
DMG file, and upload that.
Would you also like the option to edit the version number/string,  
release date, etc. manually for a version?
What would be the best practice for dealing with the actual enclosures?
- Should SparkleCaster just store the path to the enclosure and forget  
it after it's uploaded successfully?
- Or should it keep a copy for reference? Where should it keep those  
copies if it did?

Any input is greatly appreciated.

Kind Regards,

Adam Radestock
Glass Monkey Software
www.glassmonkey.co.uk