flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: [DISCUSS] Apache Flex SDK Installer 2.0 RC1
Date Tue, 01 Jan 2013 16:13:36 GMT

On 1/1/13 12:05 AM, "Justin Mclean" <justin@classsoftware.com> wrote:

> Hi,
>> Apache only officially releases (and we are voting on) a source distribution
>> for the installer.
> Would a run time loaded config file be really considered part of that source?
> Basically it's the same as the build.properties for the Flex SDK. While the
> build.properties is part of the source release kit you generally need to edit
> and change the values in it.
Build.properties is compile-time.
> The XML file is not compiled into the source it can also be changed/edited by
> the user to install other versions of the SDK or AIR. A "typical" version of
> it is included in the source (just like build.properties) see
> "sdk-insaller-config-2.0.xml"  in the root src directory.
> Would you consider the disclaimer page to be  part of the source?
The DISCLAIMER file is in the source kit for incubating releases.

> It's on the 
> wiki and linked to by the application. Or the cgi scipt it uses to get  the
> mirror? Where exactly do you draw the line?
Source kits are (potentially filtered) dumps of what is in SVN.
> Either way when a vote is called for it only requires three more +1 than -1
> votes and I don't see this as a reason for voting -1.
I'm pretty sure Apache regulations would override any vote.  This is
potentially a legal issue, so we have to get this right.  I will do more
research on the definitions of what is source.  Hopefully our mentors will
provide guidance as well.

Alex Harui
Flex SDK Team
Adobe Systems, Inc.

View raw message