at one now too.
Ken
On 2016-10-07, at 8:10 AM, Ryan Schmidt wrote:
>
>> On Oct 7, 2016, at 10:08 AM, Ken Cunningham Webuse
>> wrote:
>>
>> I think this one looks ready for prime time.
>>
>> https://trac.macports.org/ticket/52188
>
> I had bee
On 2016-10-07, at 10:05 AM, Rainer Müller wrote:
> I am not sure how we could change these to make triaging trickets easier.
I can't easily just look at the list and see what are new requests for ports to
be included in macports. It all mixed in with other things.
Also, the committer time need
I think this does it.
https://trac.macports.org/ticket/52537
Thanks!
Ken
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Very sorry -- couldn't tell. Thought it fell off the radar!
K
On 2016-10-07, at 8:10 AM, Ryan Schmidt wrote:
>
>> On Oct 7, 2016, at 10:08 AM, Ken Cunningham Webuse
>> wrote:
>>
>> I think this one looks ready for prime time.
>>
>> https://tr
I think this one looks ready for prime time.
https://trac.macports.org/ticket/52188
thanks Ken
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
DualG4s run these ports acceptably quickly. I
think the PPC buildbot builds a very good % of the current Macports.
<https://github.com/ken-cunningham-webuse/TigerPorts/blob/master/installed_Tiger_Ports_list.txt>
K
___
macports-dev mailing list
mac
On 2016-10-06, at 7:48 AM, Mojca Miklavec wrote:
> On 6 October 2016 at 16:23, René J.V. Bertin wrote:
>>
>> Ken: apologies for not having thought of this, but myself when I was still
>> running 10.6 I've had sufficient success with building C++11 code using a
>> (then) recent gcc port. It's
>
> The only blocking stone is meeting the agreement about how to
> name the new binary archives [and implementing that] :)
It would be nice if that discussion was finalized and a plan enacted.
Some of the builds on these older machines can take hours and hours...
webkit2-gtk is not even to be
