Date: Tue, 28 Jul 2020 11:36:43 +0200 (CEST) From: Ronald Klop <ronald-lists@klop.ws> To: freebsd-ports@freebsd.org Subject: Re: Chromium (& derivatives) and Python 2.7 Message-ID: <1615408980.22.1595929003688@localhost> In-Reply-To: <3075560.bT80LyP3VS@beastie.bionicmutton.org> References: <3075560.bT80LyP3VS@beastie.bionicmutton.org>
next in thread | previous in thread | raw e-mail | index | archive | help
The same problem is going to happen with mongodb36 I presume. It uses python2 to build, but does not need it to run. Would it be possible to remove python2 as a RUN_DEPENDS at the end of 2020, but keep it as a BUILD_DEPENDS in the ports framework? This might save some usefull ports. How are other projects (like Debian, etc.) solving this? Regards, Ronald. Van: Adriaan de Groot <adridg@freebsd.org> Datum: maandag, 27 juli 2020 21:36 Aan: freebsd-ports@freebsd.org Onderwerp: Chromium (& derivatives) and Python 2.7 > > The Chromium build system -- and as a consequence, also QtWebEngine -- still > uses Python 2.7. This is going to be a real problem about six months down the > line, and I have no idea how upstream is going to deal with it. I've heard > there are patches buried deep within the chocolate factory, but not from > reliable sources. > > QtWebEngine is an even specialer case, since it's an LTS and also the last LTS > in the Qt5 series, and I have real doubts about upstream -- The Qt Company -- > being able or willing to deal with Python 2.7 deprecation there. > > Has anyone in FreeBSD tried to port the stuff over? I got about an hour or two > into the porting process (making configure accept Python 3 is easy, but > there's all these wretched code-generating scripts) and hit a brick wall of > templating engines doing sensible Python 2.7 things. > > [ade] > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1615408980.22.1595929003688>