Hi,
Since some time I have some serious problem building py35-pyobjc-cocoa on 10.7.
It consumes all the available memory (it can end up with 6 GB), the
computer nearly freezes (it becomes unresponsive) and there are no
visible signs of any progress even though I usually lose the nerves
before bei
Hi Ryan,
- On 16 Nov, 2015, at 21:26, Ryan Schmidt ryandes...@macports.org wrote:
> 75% sounds like a lot. 75% of what? Are we saying that port builds take 75%
> longer?
Yes, that's what I'm saying. Last time I measured this was a very unscientific
use of time(1) and only for a single port,
Hi
It seems I'm no longer able to update my repo, using git-svn, I get
the following error:
$ git svn fetch
Can't create session: Unable to connect to a repository at URL
'https://svn.macports.org/repository/macports/trunk/dports': Error
running context: The server unexpectedly closed the connect
On Nov 16, 2015, at 3:26 PM, Ryan Schmidt wrote:
>> IMO trace mode should get faster using client-side
>> caching mechanisms, possibly shared between different processes, before we
>> enable
>> it by default.
>
> What kind of caching?
https://lists.macosforge.org/pipermail/macports-dev/2015-Ma
On Nov 16, 2015, at 14:01, Clemens Lang wrote:
> On 16 Nov, 2015, at 20:52, Ryan Schmidt wrote:
>
>> Enabling trace mode by default would solve a lot of problems. Where are we
>> with
>> that? What outstanding issues remain? Is there a (hidden?) macports.conf
>> option
>> I can use to always en
Hi,
- On 16 Nov, 2015, at 20:52, Ryan Schmidt ryandes...@macports.org wrote:
> Enabling trace mode by default would solve a lot of problems. Where are we
> with
> that? What outstanding issues remain? Is there a (hidden?) macports.conf
> option
> I can use to always enable trace mode or do
Enabling trace mode by default would solve a lot of problems. Where are we with
that? What outstanding issues remain? Is there a (hidden?) macports.conf option
I can use to always enable trace mode or do I have to remember to use the "-t"
flag with every port command?
__
On 2015-11-11 11:59, René J.V. Bertin wrote:
> Still working on those KF5 frameworks, which come in different tiers
> that correspond to the level of inter-frameworks dependencies: tier 2
> frameworks can depend on tier 1 frameworks (which don't depend on
> other KF5 stuff), tier 3 frameworks can d
