On 10/9/14, 5:21 PM, "Justin Mclean" <justinmcl...@me.com> wrote: >The second requires it being added to the SDK install scripts. This is a >little problematic in that the steps are part of each SDK release in the >dist area. I'm assuming we can't we change the contents of those without >VOTEing on a release. > >Wouldn't it be better to separate these steps from the release area and >store in the web site content like the other installer files? (eg >/installer/<productname>/<version>/config.xml) so that when things >change, like >- License terms or our understanding of those terms change >- Extra optional components are added > >We don't have to re-release packages involved?
Are you suggesting that we change the install experience for 4.13.0 and older releases? One advantage of having all of the steps in the ant script is that our Linux users (and anybody else who doesn¹t or can¹t run AIR) get a rough command-line equivalent. I think what you want to do is just chain a few installs together as in ³Hey, you¹ve installed A, would you be interested in installing B² or do you envision something more tightly integrated? Teaching the installer to chain might be useful, although again, what would we do for our Linux users? -Alex
