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 the explanation marcus. > > Can we get that list submitted as a PR, with clear instructions on the > fix procedure? Maybe even an example fix to help motivate > > I think this is a perfect opportunity to share the load, and I'll put my > hand up to help. > > Some clarity/confirmation included in the PR for the following would > also be great: > > - Can these be fixed *now* or is there something that needs to be done > first? > - What is the definition of 'proper' as you use it here? >
Hi, Do you guys have an ETA for this? We're trying to stabilize dports for Release 3.6 and all the aforementioned ports are broken. DPorts is not supposed to feature ports that can't be built so I have have to choose whether to remove them or fix them myself. I was under the impression from Marcus that the fixes were rather trivial so I figured that they would get fixed quickly. If that's not going to be the case, it would be nice to nice that as well. Thanks, John _______________________________________________ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
