ports/lang major version updates outside of OS version updates

[Dima Pasechnik]

On Sat, Apr 13, 2019 at 10:41 PM Steve Kargl
<sgk at troutmask.apl.washington.edu> wrote:
>
> On Sat, Apr 13, 2019 at 08:49:43PM +0200, Dima Pasechnik wrote:
> > On Sat, Apr 13, 2019 at 8:01 PM Steve Kargl
> > >
> > > My patches have absolutely nothing to do with making
> > > 3.6 the default python version.
> > >
> > > I have added functions to libm that are included in
> > > two ISO standards.  This causes a name conflict with
> > > sinpi() in python.  My patches trivially rename
> > > python's sinpi() to avoid the conflict.  For some reason
> > > beyond the comprehension of mortal man, python at freebsd
> > > refuses to add the patches to the port.
> >
> > they asked for these patches to be upstreamed, and I did it, so these
> > patches  now are in not yet released upstream python 2 and python 3
> > branches.
> > Backporting them to python at freebsd is totally trivial.
> >
> > What else can be done here?
>
> How about taking the patch in my previous email, apply
> to your tree (any port committer can take the patch),
> and actually commit it!
>
> This isn't rocket science.  APPLY THE PATCH AND COMMIT!

I don't have commit access to  python FreeBSD port (or any port, in fact).
---  if I had said access it would have been done months ago...

Dima

>
> --
> Steve