[Sparkle] Support for Prefpanes, Bundles, etc.

[Andy Matuschak]

I'm trying to make things a bit more generalized as I write Sparkle  
2.0. A "product" can consist of many files: an application, a  
framework, a prefpane, a bundle, etc. Each has a source path in the  
archive and a target path on the system.

Source/target data can change per-update, suggesting that this  
information should be specified per-update. It can be in the appcast,  
but that could potentially pose security issues from man-in-the-middle  
attacks.

One good alternative is to have this kind of information actually in  
the update archive, like a .sparkle.plist file. This is kinda ugly,  
but I think that with software to auto-package updates, it wouldn't be  
too bad. You'd have to let the program package your update, though,  
and it seems like a lot of people just like having their releases as  
their Sparkle builds.

Ideas?

- Andy Matuschak

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.andymatuschak.org/private.cgi/sparkle-andymatuschak.org/attachments/20070811/06f2dbf7/attachment.html