> I see what you mean, but my intent was to get flex-sdk into non-free or
> contrib first. When that's finalized, we can undertake the (rather large)
> task of getting the SDK built from source, after which point it can be moved
> into main. In my opinion, there's no point in splitting it up right now,
> since none of it can currently be built from source.
>
> If, after the SDK is built from source, there are still small pieces of it
> that can't be built from source, then a flex-sdk-nonfree would make sense,
> in my opinion.
Given that Adobe is donating Flex SDK to Apache, I'd expect all the
licensing and build issues to be cleared very soon
http://www.techworld.com.au/article/407714/adobe_donates_flex_apache
(The ASF still has to vote, but I expect the outcome will be a 'yes')
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)