On 7/20/12 3 :17PM, "Om" <bigosma...@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

Reply via email to