On Nov 7, 2018, at 01:32, Ryan Schmidt wrote:
> On Nov 6, 2018, at 17:50, Chris Jones wrote:
>
>> On 6 Nov 2018, at 11:05 pm, Ryan Schmidt wrote:
>>
>>> For Python projects that build using a setup.py file, how do I discover
>>> what options are available -- what's the equivalent of "./confi
> On Nov 6, 2018, at 1:54 PM, Ryan Schmidt wrote:
>
>
>
> On Nov 6, 2018, at 14:48, Ken Cunningham wrote:
>
>> I noticed this recently "fixing" some ports that don't use a configure step.
>>
>> During the run of portconfigure.tcl, various things (sdkroot) might be
>> tested, and the approp
What is the plan? Should we also connect this new repository with Trac?
Rainer
Forwarded Message
Subject: [GitHub] Subscribed to macports/macports-legacy-support
notifications
Date: Wed, 07 Nov 2018 12:47:03 -0800
From: GitHub
To: rai...@macports.org
Hey there, we’re just wr
On 07.11.18 22:10, Rainer Müller wrote:
> What is the plan? Should we also connect this new repository with Trac?
Ah, just found the ticket:
https://trac.macports.org/ticket/57537
Rainer
On Nov 7, 2018, at 11:00, Ken Cunningham wrote:
> On Nov 6, 2018, at 1:54 PM, Ryan Schmidt wrote:
>
>> On Nov 6, 2018, at 14:48, Ken Cunningham wrote:
>>
>>> I noticed this recently "fixing" some ports that don't use a configure step.
>>>
>>> During the run of portconfigure.tcl, various things
On Nov 7, 2018, at 15:22, Rainer Müller wrote:
> On 07.11.18 22:10, Rainer Müller wrote:
>> What is the plan? Should we also connect this new repository with Trac?
>
> Ah, just found the ticket:
> https://trac.macports.org/ticket/57537
Yes, that would be a good idea. Do we also want a new com
On 04.11.18 16:09, Mark Anderson wrote:
> I sent a message to Macports-mgr in July and haven't heard back. I know
> it can take a long time, but how long is a long time?
It is already way too long. The goal is to answer within one week.
PortMgr has failed way too often with this. In many cases it
On 2018-11-07, at 1:27 PM, Ryan Schmidt wrote:
Thanks for the detailed explanation. I do understand what you mean about
+universal. Just to point out that this port is not actually building universal
here, it's just building normally.
What I was expecting would be that portconfigure.tcl would
