+universal vs the buildbot

[Ryan Schmidt]

On Aug 29, 2012, at 06:49, Mojca Miklavec wrote:

> On Wed, Aug 29, 2012 at 5:19 AM, Ryan Stonecipher wrote:
>> Some ports have +universal as a default variant.
>> When such ports have "big" dependencies such as qt4-mac, gcc4x, or
>> atlas they take hours to build and install.
>> The buildbot makes installing default single-architecture binaries painless.
>> Could the buildbot be adapted to also provide +universal binaries with
>> default universal architectures for +universal-by-default ports and
>> their dependencies?
> 
> Or another buildbot which would try to build all the ports as universal ;)
> (or i386-only when 64-bit cannot be built ;)

The buildbot already builds ports that require 32-bit builds that way, and their dependencies universal.


> Yes, I'm aware that this would mean a lot of extra resources, but it
> would be great to have at least some huge packages built with
> +universal flag.

I'm in agreement that it would be nice to offer universal binary packages as well.


> When I tried to install TextMate2, the bottleneck was compiling
> clang-3.2. I didn't request +universal variant and I don't have any
> setting which would install +universal by default, so I'm not sure why
> it wanted recompilation from source.

TextMate2 is only available in a 32-bit version, so it requires universal dependencies.

clang-3.2 is a dependency of TextMate2 when the Xcode version is less than 4.4.

We don't appear to have any universal binaries of clang-3.2 on the packages server, nor any packages of the current version of clang-3.2 for Snow Leopard. Perhaps some build error was encountered in one or more of the packages.

We don't have any binary packages of textmate2 at all because there appears to be a license incompatibility preventing us from legally doing so:

$ port_binary_distributable.tcl -v textmate2
dependency 'openssl' has license 'OpenSSL' which conflicts with license 'gpl' from 'textmate2'