List of ports with "python 3" errors in poudriere
Kubilay Kocak
koobs.freebsd at gmail.com
Tue Oct 29 10:15:54 UTC 2013
On 29/10/2013 8:18 PM, Marcus von Appen wrote:
>
> John Marino <freebsd.contact at marino.st>:
>
>> 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 ports build
>> in poudriere again. Thanks, John
>>
>
> [broken ports]
>
> There are several more (e.g. graphics/blender), which suffer from the
> same issue.
> For those, who wonder what is going wrong here:
>
> The interim hack in bsd.python.mk, which always causes ports to pull in
> lang/python, if USE_PYTHON[_XXX] is set, is the problem. As some know, I am
> currently testing all ports for that problem and am making lang/python a
> dependency
> on the port, rather than being implicitly set by bsd.python.mk.
> Once done, the ports themselves will need to be fixed to use the proper
> python version
> rather than lang/python, so we can build version-specific packages.
>
> Long story short: No port should depend on lang/python at build and
> installation time
> as a mid-term goal.
>
> 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` :-).
>
> Cheers
> Marcus
>
>
> _______________________________________________
> freebsd-python at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-python
> To unsubscribe, send any mail to "freebsd-python-unsubscribe at freebsd.org"
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?
Koobs
More information about the freebsd-python
mailing list