[Sparkle] A Question of Enclosures

[Rob Napier]

Here are some thoughts on what the ideal app should do:

* I should be able to drop an App bundle on it (or open an App bundle from
File) and that should pull everything into a form along with reasonable
guesses on what I'd like to do (prior choices should be saved in defaults to
reuse them).

* I should then modify that form based on what I really want.

* "What I want" should include "build dmg" or "build zip" (as well as
manually setting the version, etc). Unfortunately, building DMGs really
means building custom DMGs because that's what everyone wants. And building
a system to do that in a really general and reliable and programmatic way
has been hard in my attempts for Pandoraboy.

* I don't think I would cache the enclosures if they're going to be put into
the package. The only valuable thing I could see there was saving the last
one, just to have a template to work off of (but a real template might be
better here).

-Rob

On Thu, Apr 3, 2008 at 9:41 PM, Adam Radestock <raddish at glassmonkey.co.uk>
wrote:

> 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
> _______________________________________________
> Sparkle mailing list
> Sparkle at lists.andymatuschak.org
> http://lists.andymatuschak.org/listinfo.cgi/sparkle-andymatuschak.org
>



-- 
Rob Napier -- Software and Security Consulting -- http://robnapier.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.andymatuschak.org/pipermail/sparkle-andymatuschak.org/attachments/20080403/74f08bea/attachment.htm