On Wed, Jul 20, 2011 at 06:22:31PM +0400, Ruslan Mahmatkhanov wrote:
> Anton Shterenlikht wrote on 20.07.2011 17:44:
> >On Wed, Jul 20, 2011 at 04:55:59PM +0400, Ruslan Mahmatkhanov wrote:
>
> >>As far i understand PYTHON_VERSION hold value like 'python2.7', so you
> >>should correct this in your
Anton Shterenlikht wrote on 26.07.2011 21:07:
On Wed, Jul 20, 2011 at 06:22:31PM +0400, Ruslan Mahmatkhanov wrote:
Anton Shterenlikht wrote on 20.07.2011 17:44:
On Wed, Jul 20, 2011 at 04:55:59PM +0400, Ruslan Mahmatkhanov wrote:
As far i understand PYTHON_VERSION hold value like 'python2.7'
Synopsis: Mk/bsd.python.mk: PYTHON_VERSION is ignored
Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-python
Responsible-Changed-By: edwin
Responsible-Changed-When: Tue Jul 26 20:40:16 UTC 2011
Responsible-Changed-Why:
bsd.python.mk is freebsd-python territory (via the GNATS Auto Assign
On Tue, Jul 26, 2011 at 11:46:17PM +0400, Ruslan Mahmatkhanov wrote:
> Add Mk/bsd.python.mk to description field
a good idea, but ...
> so it will be assigned to portmgr@.
portmgr@ doesn't own all the bsd.*.mk files; bsd.python.mk is owned by
python@. We're happy to put an -exp run in the queue
Mark Linimon wrote on 27.07.2011 06:44:
On Tue, Jul 26, 2011 at 11:46:17PM +0400, Ruslan Mahmatkhanov wrote:
Add Mk/bsd.python.mk to description field
a good idea, but ...
so it will be assigned to portmgr@.
portmgr@ doesn't own all the bsd.*.mk files; bsd.python.mk is owned by
python@. W