Date: Mon, 24 Aug 2020 21:01:30 -0700 From: Pete Wright <pete@nomadlogic.org> To: Kevin Oberman <rkoberman@gmail.com>, figosdev <figosdev@protonmail.com> Cc: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: Re: What are my options regarding deprecated PyPy port? Message-ID: <4eef2ee6-6fd1-7383-5031-597ff8a364f1@nomadlogic.org> In-Reply-To: <CAN6yY1tFGafzj-=viMUYHoZQMTqUjEGU=23jTz2oOc%2B1uQgzpA@mail.gmail.com> References: <SQAZKeXAUxiRGkyHyx86icqCtJIj5DiJXW_wNgamtZLSVUI3YxMXR_6S-AGzvBJQP5J8WN2wmTTiSLOeXxy9mRcopivJ5omwokBnF_9FZXI=@protonmail.com> <CAN6yY1tFGafzj-=viMUYHoZQMTqUjEGU=23jTz2oOc%2B1uQgzpA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/24/20 8:05 PM, Kevin Oberman wrote: > On Mon, Aug 24, 2020 at 6:50 PM figosdev via freebsd-ports < > freebsd-ports@freebsd.org> wrote: > >> Hi, I'm new to FreeBSD-- I installed it for the first time this week. >> Honestly, so far it has exceeded expectations. >> >> I installed X11, but the first thing I installed was PyPy2. >> >> Unlike CPython2, which is EOL'd, PyPy2 does not to the best of my >> knowledge depend on CPython. When I installed it with pkg, it said the port >> was deprecated and will be removed from ports soon-- but it also said it >> was based on Python 2.7 (which is EOLd). >> >> I think there is a misunderstanding there. PyPy states the intention to >> continue to maintain that version. >> >> Removing this port is unnecessary. Aware of the politics around this >> (which go way over FreeBSD anyway) I doubt I will convince someone to save >> this port, sadly. >> >> I've used both Python 2.x and 3.x for years now. If this problem can't be >> fixed, can I at least be put in touch with the current port maintainer so >> that I can learn how to maintain this as a 3rd party package for my own use? >> >> I'm certain I'm not up to becoming an official port maintainer at this >> stage, but I'd like to be able to at least compile and run PyPy2 on freebsd >> without redoing the ports work that was already done on this. >> > Looks like the deprecation might have been in error. While I can't be sure, > it looks like it is in no way dependent on python27 and, if it is > maintained, it probably was deprecated in error. Probably someone in the > python group saw the 2.7 references and tagged it for deprecation. > > You probably should start by contacting python@ and, if there is no > response, open a ticket on bugzilla pointing this out and requesting that > the deprecation be reversed. i agree - it looks like someone needs to refactor lang/pypy which seems to build against python2.7. there is a pypy3 port/pkg as well, but that seems to be incorrectly flagged as being deprecated according to freshports. i searched bugzilla too but only found an open cleanup ticket there: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245747 -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4eef2ee6-6fd1-7383-5031-597ff8a364f1>