Hi, I been looking at adding Flex Unit to the installer and it occurred to me that we may want to add it in two places. 1. As a stand alone product (ie shows in first list along with the various SDKS) 2. As an optional part of installing an SDK
1 makes sense if you have already installed the SDK., 2 make sense if you haven't have installed the SDK. You could of course just manually download and unzip it - but having everything accessible via the installer make sense to me. The first requires a few changes to the installer as it currently assumes an ant script must be run, but to just download, check the MD5 and uncompress something no ant file is required as the installer does that for you. I've made but not fully tested the required installer changes for that. 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? Thanks, Justin
