Re: Change version number of python built-in module packages

[Thomas Klausner <wiz%NetBSD.org@localhost>]

On Tue, Jun 04, 2013 at 09:14:10AM +0900, OBATA Akio wrote:
> On Tue, 04 Jun 2013 07:29:53 +0900, Thomas Klausner 
> <wiz%netbsd.org@localhost> wrote:
> 
> >On Mon, Jun 03, 2013 at 08:25:34PM +0100, Jonathan Perkin wrote:
> >>* On 2013-04-12 at 12:01 BST, OBATA Akio wrote:
> >>
> >>> Currently, version number of python built-in module packages
> >>> is fixed as 0:
> >>>   databases/py-sqlite3
> >>>   devel/py-curses
> >>>   devel/py-cursespanel
> >>>   devel/py-readline
> >>>   textproc/py-expat
> >>>   textproc/py-cElementTree
> >>>   x11/py-Tk
> >>>
> >>> I feel it should be changed to use base python version ${PY_DISTVERSION
> >>> (same as Ruby and PHP modules), or those packages will not be updated
> >>> even if update of Pyhon base distribution contains fixes for such modules.
> >>>
> >>> Any comments/suggestins/objections?
> >>
> >>This broke pbulk:
> >>
> >>  pbulk-resolve: No match found for dependency py26-Tk>=2.7.5nb1 of package 
> >> py26-OpenGL-3.0.1nb2
> >>  pbulk-resolve: No match found for dependency py26-Tk>=2.7.5nb1 of package 
> >> py26-imagingtk-1.1.7nb4
> >>  pbulk-resolve: No match found for dependency py26-Tk>=2.7.5nb1 of package 
> >> py26-matplotlib-tk-1.2.0nb2
> >>
> >>The problem is py-Tk's buildlink3.mk:
> >>
> >>  BUILDLINK_ABI_DEPENDS.pytk+=    ${PYPKGPREFIX}-Tk>=2.7.5nb1
> >>
> >>which needs to be changed to use PY_DISTVERSION instead, but I do not
> >>off-hand know of a clean way to do this.  This originated due to a
> >>revbump, so it's possible the revbump tools will need fixing too to
> >>understand this versioning scheme.
> >>
> >>Please fix.
> >
> >I don't see an easy fix.
> >
> >On the other hand, the whole contents of py-Tk is one dynamically
> >loadable module, so I don't think a buildlink3.mk file is appropriate
> >or necessary.
> >
> >I suggest replacing it, where included, with a plain
> >  DEPENDS+= ${PYPKGPREFIX}-Tk-[0-9]*:../../x11/py-Tk
> >line.
> 
> Yes, it's the fix, and py-Tk/buildlink3.mk must be removed.
> 
> >Does anyone see a problem with that?
> 
> I was doing such clean up over a year ago (from a to z, probably
> suspended in textproc/*).
>   http://mail-index.netbsd.org/pkgsrc-wip-discuss/2012/01/30/msg002111.html
> 
> If someone have a time, please do it for remaining packages...

I've done it for the packages mentioned above.
 Thomas