So one of the goals of rewriting the installer is to get us out of the business of needing to create platform-dependent artifacts. Ideally, the next release of the Apache Flex Installer would be the last one ever. All further installs are done by having the Installer execute an ant script in a GUI-like way. That's because I don't think any of us except maybe Justin have the ability to produce the artifacts for each platform.
So, I have in mind two scenarios: 1) You already have Ant installed, you download the .zip or .tar.gz from the Apache Flex downloads page, expand it manually, run "ant install" and get console output as the install runs. 2) You have downloaded and installed the Apache Flex Installer so you just run it, you get a choice of .zip or .tar.gz files to download, choose a language, choose FP versions, AIR versions, and get a GUI experience as the install runs. Now if there is a way to further package the other information you mention into Linux packages without requiring Linux (like .DEB is just an archive format), then I could see us doing that alongside the .zip and .tar.gz files. Thanks, -Alex On 1/3/14 1:19 AM, "Tom Chiverton" <t...@extravision.com> wrote: >On 02/01/2014 18:06, Alex Harui wrote: >> OK. I'm essentially ignorant as to how installs happen on Linux. If >>you >> have time, can you try to get the installer.xml files to run for >> flex-falcon/flex-asjs on Linux? >It's a bit like .dmg on MacOS in that a single file contains the >dependency and metadata information and the application code, as opposed >to Win32 where the .exe installer contains the application as well as >installers for all it's possible dependencies. >In addition, Linux users expect their packages (of which, naturally, >there are two competing formats) to be organised and distributed via >repositories (which are just web servers with a particular layout and >meta data.). > >I'll try and at least do an initial run of the installer.xml tonight. >Note to self : http://goo.gl/Hxbu8q > >Tom
