On Tue, Jul 23, 2013 at 08:33:16PM +0200, Freek Dijkstra wrote:
> I'm happy to file a bug report, but what is the proper behaviour in
> this case?
>
> The binary of the py32-Pillow package depends on a variant in another
> package (the python32 package). How should MacPorts distinguish
> between t
On 23-07-2013 18:04, Clemens Lang wrote:
>> Is there a way to enforce building of a package, thus disabling
>> downloads of precompiles binary archives?
>
> Use port -s or set buildfromsource always in macports.conf
Thanks Clemens & Jeremy! port -s worked like a charm.
(I now see it is in the ma
On Tue, Jul 23, 2013 at 06:02:49PM +0200, Freek Dijkstra wrote:
> Is there a way to enforce building of a package, thus disabling
> downloads of precompiles binary archives?
Use port -s or set buildfromsource always in macports.conf
> PS: for those wondering why (as a precompiled package is usual
Two options.
Per command:
sudo port -s ...
Globally in macports.conf:
# When to build ports from source. Default is 'ifneeded', which downloads an
# archive if available or builds from source otherwise. 'always' has the same
# effect as -s on the command line, and 'never' is likewise the same as
Hi,
Is there a way to enforce building of a package, thus disabling
downloads of precompiles binary archives?
I expected that "port build" following by "port install" to work, but it
still seems to download a precompiled version:
> ~# port build py32-pillow
> ---> Computing dependencies f
