On Aug 7, 2011, at 2:04 PM, Michael Gersten wrote:
>> That is true, when they are related. But I have also had a bunch of times
>> where two ports at both outdated, and are not at all related. But, by
>> default, macports stops when port A gives an error, so it never gets to
>> build B, even
That is true, when they are related. But I have also had a bunch of
times where two ports at both outdated, and are not at all related.
But, by default, macports stops when port A gives an error, so it
never gets to build B, even though there is no dependency.
In those cases, I will do:
s
On Jun 18, 2011, at 12:39 PM, Ryan Schmidt wrote:
>
> On Jun 18, 2011, at 05:12, David Nicholls wrote:
>
>> I know this has been answered before, but I have lost the post where it was
>> described (and cannot find it in the Guide): how do I bypass a port which
>> has install problems so tha
On Jun 18, 2011, at 05:12, David Nicholls wrote:
> I know this has been answered before, but I have lost the post where it was
> described (and cannot find it in the Guide): how do I bypass a port which
> has install problems so that I can continue upgrading other outdated ports?
Bear in mind
-p Despite any errors encountered, proceed to process multiple
ports and commands.
On Jun 18, 2011, at 3:12 AM, David Nicholls wrote:
> I know this has been answered before, but I have lost the post where it was
> described (and cannot find it in the Guide): how do I b
I know this has been answered before, but I have lost the post where it
was described (and cannot find it in the Guide): how do I bypass a port
which has install problems so that I can continue upgrading other
outdated ports?
Thanks
DN
--
__
ANU RSAA Mt Stromlo
__
