Date: Wed, 15 Jan 2014 21:24:02 +0100 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Mike Brown <mike@skew.org> Cc: freebsd-ports@freebsd.org Subject: Re: USE_PYTHON version range no longer valid? Message-ID: <20140115202401.GB39030@ithaqua.etoilebsd.net> In-Reply-To: <201401151947.s0FJlOCG004035@chilled.skew.org> References: <201401151947.s0FJlOCG004035@chilled.skew.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--6sX45UoQRIJXqkqR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 15, 2014 at 12:47:24PM -0700, Mike Brown wrote: > A port I maintain (sorta) can only be built under Python 2.2.1 through 2.= 4.x. > The app isn't being developed any longer, so patches to get it to build u= nder > 2.5+ aren't likely to be forthcoming. >=20 > The port Makefile previously had USE_PYTHON=3D 2.2-2.4, but it was change= d this=20 > week to simply USE_PYTHON=3D2, with this comment: >=20 > Python cleanup: > - USE_PYTHON* =3D 2.X -> USE_PYTHON* =3D 2 > - USE_PYTHON* =3D 2.X+ -> USE_PYTHON* =3D yes > Reviewed by: python (mva, rm) > Approved by: portmgr-lurkers (mat) >=20 That means that port should either be removed from the ports tree, or one s= hould fork it and port it to newer version of python. Python 2.4- are EOLed upstream for long, we are respecting upstream, so the= re nothing more we can do about it. regards, Bapt --6sX45UoQRIJXqkqR Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (FreeBSD) iEYEARECAAYFAlLW7mEACgkQ8kTtMUmk6ExwFACgnmQM95dhTvo8B2QXeH1/N95T tYoAnRZ0qneqJdfCc1eUvl+DVQbgx5JM =o1LB -----END PGP SIGNATURE----- --6sX45UoQRIJXqkqR--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140115202401.GB39030>