On Sat, Dec 10, 2011 at 6:49 AM, Remi Pointel remi.poin...@xiri.fr wrote:
Hi,
I reworked on the diff to update python.port.mk to permit to have both Python
2.x and 3.x working on OpenBSD.
How it works:
1) Python2 port
- all ports existing don't need to change, they still build with Python
[..]
Finally, can you add a _ in MODPY_DEFAULT_VERSIONX before 2 and 3?
It easy to mix the number otherwise.
I meant easy to miss.
f.-
Hi,
I reworked on the diff to update python.port.mk to permit to have both Python
2.x and 3.x working on OpenBSD.
How it works:
1) Python2 port
- all ports existing don't need to change, they still build with Python 2
2) Python2 and Python3 port
- if you know that a port (and its
Hi, I have worked on the diff.
Differences with last diff I sent are:
- use PY3 instead of IS_PY3
- PY3 could be:
* both if it works with python 2 and python 3 (instead of yes)
* only if it works only with python 3
- modify FLAVORS, it was not correct
I run a build (amd64) on all ports which
On Mon, Nov 21, 2011 at 08:24:52PM +0100, Remi Pointel wrote:
Hi, I have worked on the diff.
Differences with last diff I sent are:
- use PY3 instead of IS_PY3
- PY3 could be:
* both if it works with python 2 and python 3 (instead of yes)
I'm ok with the diff, but I find the following a
On Wed, Nov 16, 2011, Marc Espie wrote:
I've mostly said away from the ruby stuff because I don't really care, but
I find the 4 distinct implementations of dubious values. The fact there is
no apparent consensus as to which one is the best, well, that's not exactly
a sign of language
Hi,
this is the diff to update python.port.mk to permit to have both Python 2.x and
3.x working on OpenBSD.
How it works:
1) Python2 port
- all ports existing don't need to change, they still build with Python 2
2) Python2 and Python3 port
- if you know that a port (and its dependencies...)
I think this is a very clever yet simple approach, I like it.
A bulk is needed with this to make sure everything still builds the same way,
before doing any of the IS_PY3 change.
Good work!
On Wed, Nov 16, 2011 at 05:09:41PM +0100, Remi Pointel wrote:
Hi,
this is the diff to update
On Wed, Nov 16, 2011 at 5:09 PM, Remi Pointel remi.poin...@xiri.fr wrote:
Hi,
this is the diff to update python.port.mk to permit to have both Python 2.x
and 3.x working on OpenBSD.
How it works:
1) Python2 port
- all ports existing don't need to change, they still build with Python 2
On Wed, Nov 16, 2011 at 06:12:50PM +0100, Jeremy Evans wrote:
FLAVORs. This approach avoids that issue, so an upgrade from python
3.2 to 3.3 would only require you bump the ports that are specifically
set to build with python 3. The only downside is if you want to
support another python
On 2011-11-16, Remi Pointel remi.poin...@xiri.fr wrote:
So, if your ports use:
1) Python 2 only
- nothing to change
2) Python 2 and Python 3:
- add IS_PY3 = Yes
- add to your *_DEPENDS : ${MODPY_FLAVOR}, without comma (example:
BUILD_DEPENDS: devel/py-distribute${MODPY_FLAVOR}).
- make
On Wed, Nov 16, 2011 at 6:27 PM, Marc Espie es...@nerim.net wrote:
On Wed, Nov 16, 2011 at 06:12:50PM +0100, Jeremy Evans wrote:
FLAVORs. This approach avoids that issue, so an upgrade from python
3.2 to 3.3 would only require you bump the ports that are specifically
set to build with python
12 matches
Mail list logo
