pkg-plist %%PYVER%%.%%PYOEXTENSION%% handling. patch included, feedback needed

[clutton]

On Tue, 2016-01-05 at 03:30 +1100, Kubilay Kocak wrote:
> On 5/01/2016 2:50 AM, clutton wrote:
> > On Tue, 2016-01-05 at 02:37 +1100, Kubilay Kocak wrote:
> > > On 5/01/2016 2:35 AM, clutton wrote:
> > > > On Tue, 2016-01-05 at 02:26 +1100, Kubilay Kocak wrote:
> > > > > On 5/01/2016 2:13 AM, clutton wrote:
> > > > > > Hi list.
> > > > > > 
> > > > > > As I can see there are two ways of doing pkg-plist routine.
> > > > > > 
> > > > > > For pkg-plist which was made for python2 just including
> > > > > > USE_PYTHON=	
> > > > > > py3kplist would do the trick.
> > > > > > 
> > > > > > For new python3 ports it's not so straight forward, and
> > > > > > when
> > > > > > they
> > > > > > don't
> > > > > > use setup.py conventions people usually do something like
> > > > > > this:
> > > > > > 
> > > > > > .if ${PYTHON_REL} < 3500
> > > > > > PYOEXTENSION=	pyo
> > > > > > .else
> > > > > > PYOEXTENSION=	opt-1.pyc
> > > > > > .endif
> > > > > > 
> > > > > > PLIST_SUB+=	PYOEXTENSION=${PYOEXTENSION} \
> > > > > > 		PYVER=${PYTHON_VER:S/.//}
> > > > > > 
> > > > > > 
> > > > > 
> > > > > Currently an in-progress issue:
> > > > 
> > > > I see. The name convention and approach are even better then
> > > > my.
> > > > Thank you.
> > > > 
> > > 
> > > You're welcome, and feel free to add your thoughts/comments to
> > > that
> > > issue as well.
> > > 
> > > ./koobs
> > 
> > Only porters-handbook updating, as soon it'll be commited. Handbook
> > always goes behind ports tree and sometime it's hard to follow for
> > people who contribute occasionally.
> > 
> 
> That's the nature of a fast moving beast :)
> 

What prevent this from being commited? Could this time be shortened?