You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Om <bi...@gmail.com> on 2012/07/20 20:34:11 UTC
InstallApacheFlex - TODO
On Fri, Jul 20, 2012 at 7:50 AM, Nicholas Kwiatkowski <ni...@spoon.as>wrote:
> It's not really apart of the release, so I don't think so, but we should be
> able to create another place for it to exist.
>
> BTW: Is the installer final? I'd like to post it on the website as well.
>
> -Nick
>
>
Here are the outstanding items for the installer. In the interest of time,
it would be great if folks pick items from this list and get it done.
1. Build auto-update mechanism (Om + Carol)
I would like help with these items:
2. Use closer.cgi to automatically pick a download mirror. The app must
somehow get the preferred mirror url. The closer.cgi, ex:
http://www.apache.org/dyn/closer.cgi/incubator/flex/4.8.0-incubating/apache-flex-sdk-4.8.0-incubating-src.zipreturns
a html which contains a link to a preferred mirror. We should
probably parse the html in the app to grab the preferred url? Anyone knows
of a better approach? The documentation is here:
http://www.apache.org/dev/mirrors.html
3. Signing the binaries the Apache way. I was hoping to learn the
process, but if Carol can do it for this release, that would be great. In
any case, I dont have access to a Mac, and I dont think I should be signing
artifacts that I personally did not generate.
4. The installer app needs to programatically verify the downloaded flex
binaries' signatures. I have very little experience with crypto
algorithms. Can someone take this up? Even if someone can explain the
steps to do this, I can get it done.
5. Signing the binaries the Adobe AIR way. This process will allow us to
have Apache Flex (or ASF) as the publisher ID in the installer. This makes
the installer app look more reliable for end users.
I am engaged in a discussion about this process in the @infra-dev list. I
am not sure when this might be set up for us. I dont think we can afford
to delay the release of the app for this feature. Or should we wait?
Thanks,
Om
Re: InstallApacheFlex - TODO
Posted by Carol Frampton <cf...@adobe.com>.
On 7/20/12 3 :17PM, "Om" <bi...@gmail.com> wrote:
>>>4. The installer app needs to programatically verify the downloaded
>>>flex
>> >binaries' signatures. I have very little experience with crypto
>> >algorithms. Can someone take this up? Even if someone can explain the
>> >steps to do this, I can get it done.
>>
>> Are you going to check the signature (.asc) or the checksum (.md5)? I'm
>> sure the later is much easier.
>>
>>
>.md5 it is, then ;-) As I said, I dont know how to go about doing this
>(yet) I will do some research on this when I get a chance.
It looks like com.adobe.com.crypto.MD5Stream in
https://github.com/mikechambers/as3corelib will do what you need. It has
a BSD license so we can use it with no issues.
Carol
Re: InstallApacheFlex - TODO
Posted by Carol Frampton <cf...@adobe.com>.
On 7/20/12 3 :17PM, "Om" <bi...@gmail.com> wrote:
>>
>> >1. Build auto-update mechanism (Om + Carol)
>>
>> release/version.xml is now being generated. You/someone needs to fix
>> installer.url.win/installer.url.mac in build.properties.
>>
>> Awesome! I will get working on the update mechanism.
>What exactly needs to be done to get the appropriate urls in version.xml?
>Is that something we can hardcode for now? Of course, the app will still
>have to resolve the appropriate mirror via closer.cgi.
Fix these two propertues in build.properties. Whatever is there goes into
release/version.xml.
#The URLs for the IDE Installer Apps
installer.url.win=TBD_WIN
installer.url.mac=TBD_MAC
which currently gets generated looking like:
<?xml version="1.0"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<update>
<!-- The URL to download the Windows installer from -->
<urlWindows>TBD_WIN</urlWindows>
<!-- The URL to download the Mac installer from -->
<urlMac>TBD_MAC</urlMac>
<!-- The version from InstallApacheFlex-app.xml -->
<version>0.7.1</version>
<description>Latest release</description>
<required>true</required>
</update>
>
>
>> >
>> >3. Signing the binaries the Apache way. I was hoping to learn the
>> >process, but if Carol can do it for this release, that would be great.
>> In
>> >any case, I dont have access to a Mac, and I dont think I should be
>> >signing
>> >artifacts that I personally did not generate.
>>
>> I can do this when it is time.
>>
>>
>Cool. Do you have access to both Windows and Mac machines? You will be
>able to sign both the binaries, right?
I have vmware for my Windows machine. I try to use Windows as little as
possible but I did just build the app there to make sure I didn't break
anything.
>
>
>> >
>> >4. The installer app needs to programatically verify the downloaded
>>flex
>> >binaries' signatures. I have very little experience with crypto
>> >algorithms. Can someone take this up? Even if someone can explain the
>> >steps to do this, I can get it done.
>>
>> Are you going to check the signature (.asc) or the checksum (.md5)? I'm
>> sure the later is much easier.
>>
>>
>.md5 it is, then ;-) As I said, I dont know how to go about doing this
>(yet) I will do some research on this when I get a chance.
>
>Thanks,
>Om
Re: InstallApacheFlex - TODO
Posted by Om <bi...@gmail.com>.
>
> >1. Build auto-update mechanism (Om + Carol)
>
> release/version.xml is now being generated. You/someone needs to fix
> installer.url.win/installer.url.mac in build.properties.
>
> Awesome! I will get working on the update mechanism.
What exactly needs to be done to get the appropriate urls in version.xml?
Is that something we can hardcode for now? Of course, the app will still
have to resolve the appropriate mirror via closer.cgi.
> >
> >3. Signing the binaries the Apache way. I was hoping to learn the
> >process, but if Carol can do it for this release, that would be great. In
> >any case, I dont have access to a Mac, and I dont think I should be
> >signing
> >artifacts that I personally did not generate.
>
> I can do this when it is time.
>
>
Cool. Do you have access to both Windows and Mac machines? You will be
able to sign both the binaries, right?
> >
> >4. The installer app needs to programatically verify the downloaded flex
> >binaries' signatures. I have very little experience with crypto
> >algorithms. Can someone take this up? Even if someone can explain the
> >steps to do this, I can get it done.
>
> Are you going to check the signature (.asc) or the checksum (.md5)? I'm
> sure the later is much easier.
>
>
.md5 it is, then ;-) As I said, I dont know how to go about doing this
(yet) I will do some research on this when I get a chance.
Thanks,
Om
Re: InstallApacheFlex - TODO
Posted by Carol Frampton <cf...@adobe.com>.
One more thing I just noticed since I actually used the generated SDK to
try to reproduce a bug which just came in.
On the Mac, the binary files from the SDK have lost their execute mode.
The binary files from the AIR SDK did not. I suspect it is because you
are using unzip for the Flex SDK and untar for the AIR SDK.
This means, for example, that you can't execute mxmlc from the command
line.
Carol
On 7/20/12 2 :34PM, "Om" <bi...@gmail.com> wrote:
>Here are the outstanding items for the installer. In the interest of
>time,
>it would be great if folks pick items from this list and get it done.
>
>1. Build auto-update mechanism (Om + Carol)
>
>I would like help with these items:
>
>2. Use closer.cgi to automatically pick a download mirror. The app must
>somehow get the preferred mirror url. The closer.cgi, ex:
>http://www.apache.org/dyn/closer.cgi/incubator/flex/4.8.0-incubating/apach
>e-flex-sdk-4.8.0-incubating-src.zipreturns
>a html which contains a link to a preferred mirror. We should
>probably parse the html in the app to grab the preferred url? Anyone
>knows
>of a better approach? The documentation is here:
>http://www.apache.org/dev/mirrors.html
>
>3. Signing the binaries the Apache way. I was hoping to learn the
>process, but if Carol can do it for this release, that would be great. In
>any case, I dont have access to a Mac, and I dont think I should be
>signing
>artifacts that I personally did not generate.
>
>4. The installer app needs to programatically verify the downloaded flex
>binaries' signatures. I have very little experience with crypto
>algorithms. Can someone take this up? Even if someone can explain the
>steps to do this, I can get it done.
>
>5. Signing the binaries the Adobe AIR way. This process will allow us to
>have Apache Flex (or ASF) as the publisher ID in the installer. This
>makes
>the installer app look more reliable for end users.
>I am engaged in a discussion about this process in the @infra-dev list. I
>am not sure when this might be set up for us. I dont think we can afford
>to delay the release of the app for this feature. Or should we wait?
>
>Thanks,
>Om
Re: InstallApacheFlex - TODO
Posted by Carol Frampton <cf...@adobe.com>.
On 7/20/12 2 :34PM, "Om" <bi...@gmail.com> wrote:
>On Fri, Jul 20, 2012 at 7:50 AM, Nicholas Kwiatkowski
><ni...@spoon.as>wrote:
>
>> It's not really apart of the release, so I don't think so, but we
>>should be
>> able to create another place for it to exist.
>>
>> BTW: Is the installer final? I'd like to post it on the website as well.
>>
>> -Nick
>>
>>
>Here are the outstanding items for the installer. In the interest of
>time,
>it would be great if folks pick items from this list and get it done.
>
>1. Build auto-update mechanism (Om + Carol)
release/version.xml is now being generated. You/someone needs to fix
installer.url.win/installer.url.mac in build.properties.
>
>I would like help with these items:
>
>2. Use closer.cgi to automatically pick a download mirror. The app must
>somehow get the preferred mirror url. The closer.cgi, ex:
>http://www.apache.org/dyn/closer.cgi/incubator/flex/4.8.0-incubating/apach
>e-flex-sdk-4.8.0-incubating-src.zipreturns
>a html which contains a link to a preferred mirror. We should
>probably parse the html in the app to grab the preferred url? Anyone
>knows
>of a better approach? The documentation is here:
>http://www.apache.org/dev/mirrors.html
>
>3. Signing the binaries the Apache way. I was hoping to learn the
>process, but if Carol can do it for this release, that would be great. In
>any case, I dont have access to a Mac, and I dont think I should be
>signing
>artifacts that I personally did not generate.
I can do this when it is time.
>
>4. The installer app needs to programatically verify the downloaded flex
>binaries' signatures. I have very little experience with crypto
>algorithms. Can someone take this up? Even if someone can explain the
>steps to do this, I can get it done.
Are you going to check the signature (.asc) or the checksum (.md5)? I'm
sure the later is much easier.
>
>5. Signing the binaries the Adobe AIR way. This process will allow us to
>have Apache Flex (or ASF) as the publisher ID in the installer. This
>makes
>the installer app look more reliable for end users.
>I am engaged in a discussion about this process in the @infra-dev list. I
>am not sure when this might be set up for us. I dont think we can afford
>to delay the release of the app for this feature. Or should we wait?
>
>Thanks,
>Om