Sparkle 2.0: Support for Weird Products

Lots of people make weird things like bundles, prefpanes, and menu items.

Therefore, Sparkle 2.0 will have the functional unit of a "product." When registering an application, one provides a bundle path from which Sparkle reads the necessary data. When an update is delivered, the default behavior is to replace the bundle at the provided path with a bundle of the same name in the update. If that can't be done, Sparkle looks for a .pkg in the delivered update and runs it. This can take care of installing updates for more complicated programs.

Will that suit everyone's needs? I know it kind of sucks to have to make a .pkg all the time for your updates, but I can't think of an alternative that doesn't involve essentially reimplementing a large subset of Installer.app's infrastructure.