[ Joshua Root wrote on Wed 26.Sep'12 at 4:13:12 +1000 ]
> On 2012-9-26 04:05 , Kenneth Miller wrote:
> > Why does macports insist on using only local builds?
>
> It doesn't. If a prebuilt package is available, it will be used. There
> are a number of reasons why one might not be.
As a Mac OS X
orts-users@lists.macosforge.org"
; "macports-...@lists.macosforge.org"
Sent: Tuesday, September 25, 2012 1:14 PM
Subject: Re: Prebuilt alternatives
On Tue, Sep 25, 2012 at 2:05 PM, Kenneth Miller
wrote:
Why does macports insist on using only local builds? I mean, this is a lo
Hi,
> (b) If you are on a supported platform (currently 10.6 / 10.7 Intel x86 /
> x86-64) using default variants and with default install path, *and* the
> port's license permits binary redistribution, *and* you have not forced
> source only with -s or the appropriate macports.conf configuratio
On Tue, Sep 25, 2012 at 2:05 PM, Kenneth Miller wrote:
> Why does macports insist on using only local builds? I mean, this is a lot
> like gentoo, where you download and
>
(a) Gentoo, like MacPorts, is inspired by *BSD ports which is build from
source.
(b) If you are on a supported platform (cu
On 2012-9-26 04:05 , Kenneth Miller wrote:
> Why does macports insist on using only local builds?
It doesn't. If a prebuilt package is available, it will be used. There
are a number of reasons why one might not be.
- Josh
___
macports-users mailing list
