[CMake] CPack Generator for the Mac App Store

[clinton at elemtech.com]

Bringing this thread back to the cmake list... 

----- Original Message -----

> Hi Clint,

> On Fri, Apr 12, 2013 at 9:28 AM, Clinton Stimpson < clinton at elemtech.com >
> wrote:
> > Ok, I now see what is special about it.
> 
> > It uses "productbuild" to generates a .pkg (which is then put inside a
> > .dmg),
> 

> The pkg file is not put inside a dmg image, it's uploaded to the App Store
> via a piece of software called "Application Loader".
> Basically you have a MySoftware.app Bundle inside a .pkg file.

Oh. So no .dmg. That is interesting -- oh wait, its creating a "flat" .pkg file, right? 
The PackageMaker generator also creates .pkg files, but they are not flat. They are directories that can be navigated into much like a .app. 

The man page for productbuild says it also makes a product archive for the OS X Installer. Last time I looked at PackageMaker a few months back (while trying to fix postflight script support in component mode), I wondered about modifying it to use productbuild internally after realizing that the packagemaker tool was deprecated. But after having this discussion, I realize its good to have a new generator instead of modifying the PackageMaker generator. 

> I'll admit my understanding of the App Store is somewhat limited, I've
> learned what I need in order to submit my application. So I'm sure there are
> gaps in my knowledge.

> > I haven't been keeping up with all the
> 
> > Mac updates (nor am I really a Mac developer), but isn't productbuild the
> > new
> 
> > replacement for PackageMaker?
> 

> I've never used PackageMaker, but a quick google makes it look like
> productbuild is the successor.

> > How about calling it a ProductBuild generator? Or is it really specific to
> > the
> 
> > app store?
> 

> This work flow appears to be specific to the app store.

Does this workflow in your MacAppStore generator include anything that prevents making a .pkg for OS X Installer?