On 20/11/2013 09:25, Justin Mclean wrote:
> > I think it's quite a hurdle so some clear docs are a good start.
No argument there.
If someone grants my user create pages permission on the Wiki I'll put
something under Guides and Reference to start with.
That would be the best way forward, I looked into it in the past (for ubuntu)
but there's a
reasonable amount of work involved and I know very about making Linux packages.
I built a script into a PPA
(https://launchpad.net/~bugs-launchpad-net-falkensweb/+archive/remove-old-kernels)
so have all the gubins set up already.
I don't imagine something similar to RPM systems would be too much hassle.
We'd need to unpack the Flex installer .deb, and add a post install
script, then rebuild and resign it (not the .air app itself, that stays
untouched).
I can look into giving this a go later this week; if it works locally
I'll spin up a PPA.
The post install script is fairly simple as far as I can tell
* check for the AIR runtime libraries
* if found exit
* wget the .deb for the runtime
* dpkg -i it
* ln -s the broken locations
If Apache ever gets a redist licence, we can simply include the runtime
in the same PPA, and then the installer can express a dependency on the
the runtime that will be automatically resolved (I think).
Tom
