On 11/3/2013 16:24, William Grzybowski wrote:
> Hi,
>
> Can you please give it another go with r332618?
>
Hi William,
That simple one-liner worked like magic.
Thanks!
John
___
freebsd-python@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis
Hi,
Can you please give it another go with r332618?
Cheers
On Tue, Oct 29, 2013 at 6:42 AM, John Marino wrote:
> Per IRC conversation with mva, I'm sending python@ a list of ports that
> currently don't build in DragonFly poudriere due to ports infrastructure
> problems. I have not changed the
Kubilay Kocak :
On 29/10/2013 8:18 PM, Marcus von Appen wrote:
John Marino :
Per IRC conversation with mva, I'm sending python@ a list of ports that
currently don't build in DragonFly poudriere due to ports infrastructure
problems. I have not changed the python default in make.conf. It wo
On 10/29/2013 11:15, Kubilay Kocak wrote:
> On 29/10/2013 8:18 PM, Marcus von Appen wrote:
>>
>> For those with too much free time at their hands: feel free to go
>> through John's list
>> and fix the ports to use a proper python version at build time instead
>> of `python` :-).
>>
>
> Thanks for
On 29/10/2013 8:18 PM, Marcus von Appen wrote:
>
> John Marino :
>
>> Per IRC conversation with mva, I'm sending python@ a list of ports that
>> currently don't build in DragonFly poudriere due to ports infrastructure
>> problems. I have not changed the python default in make.conf. It would
>>
John Marino :
Per IRC conversation with mva, I'm sending python@ a list of ports that
currently don't build in DragonFly poudriere due to ports infrastructure
problems. I have not changed the python default in make.conf. It would
be nice to get Mk/bsd.python.mk (or whatever) fixed so these po
