Date: Sat, 13 Apr 2019 20:49:43 +0200 From: Dima Pasechnik <dimpase+freebsd@gmail.com> To: FreeBSD Ports <freebsd-ports@freebsd.org> Cc: Roger Marquis <marquis@roble.com> Subject: Re: ports/lang major version updates outside of OS version updates Message-ID: <CAAWYfq0Y7_SXJM3rspXN1mRzyyzxYayE1Upb4xZQmv1rNdpB4Q@mail.gmail.com> In-Reply-To: <20190413175954.GA29960@troutmask.apl.washington.edu> References: <nycvar.OFS.7.76.444.1904130714130.10594@mx.roble.com> <20190413175954.GA29960@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Apr 13, 2019 at 8:01 PM Steve Kargl <sgk@troutmask.apl.washington.edu> wrote: > > On Sat, Apr 13, 2019 at 07:35:25AM -0700, Roger Marquis wrote: > > >> On Fri, Apr 12, 2019 at 11:18:50PM +0200, Dima Pasechnik wrote: > > >>> So there is more "software bureaucracy" here than just applying one patch. > > > > You sure about that Dima? Whether one or several the patching doesn't > > appear to be complicated or difficult to maintain. > > > > > On Fri, Apr 12, 2019 at 02:58:22PM -0700, Steve Kargl wrote: > > > For those people following along in the mailing list, Dima > > > sent me a private reply that took this thread off the list. > > > I am done trying to help fix the python ports. > > > > Thanks for the good work Steve. > > > > Many of us are still wondering why this change was made outside of a > > major OS version update. Wouldn't that have prevented the build bug > > which started this thread? > > > > Considering the incompatibilities between python 2.X and 3.x (which > > Guido has admitted was a mistake) please consider this a ports policy > > request to require significant lang/* version updates be predicated on > > equally significant OS version updates. > > > > 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@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@freebsd is totally trivial. What else can be done here? I can add these patches to the bug tracker... Dima > > -- > Steve > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAAWYfq0Y7_SXJM3rspXN1mRzyyzxYayE1Upb4xZQmv1rNdpB4Q>