Date: Fri, 26 Mar 2021 14:55:15 -0500 From: Greg Rivers <gcr+freebsd-ports@tharned.org> To: freebsd-ports@freebsd.org Subject: Re: Python 2.7 removal outline Message-ID: <12069577.xkLNZX5ndW@no.place.like.home> In-Reply-To: <14A27037-4174-4708-9AE3-16D599076639@gushi.org> References: <20210324130347.GA29020@freefall.freebsd.org> <8552dddf3bc33e42ae124cd4ea53fb4f@bsdforge.com> <14A27037-4174-4708-9AE3-16D599076639@gushi.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 26 March 2021 14:19:20 CDT Dan Mahoney (Ports) wrote: > More thoughts on mailman, specifically: >=20 > So, I just went to find an old FB post I made about mailman 2.x: >=20 > =3D=3D=3D > From the "Load Bearing B****it" department: > Pretty much the entire world is stuck using an EOL'd mailing list manager= (mailman 2.x), which depends on an EOL'd python (2.7). =20 > This includes: > * All the gnu mailing lists > * All of the linux mailing lists at listman.redhat > * all the FreeBSD mailing lists > * all the sourceforge mailing lists > * all the IETF mailing lists > * all of lists.isc.org > * NANOG > =3D=3D=3D >=20 > That=E2=80=99s an AWFUL LOT of sysadmins, network admins, and coders who = looked long and hard at Mailman 3 and decided =E2=80=9Cthat=E2=80=99s not r= eady yet=E2=80=9D. >=20 > I think, if *nothing else*, tauthon needs to be stapled in for mailman, e= ven if it lives under /usr/local/mailman/bin or something (and bakes in the= couple of dependencies). >=20 > I know about the archive incompatibility. There *might* be a GSOC projec= t to fix it. Maybe. Other changes can happen with greater use, but clearl= y there=E2=80=99s a first-mover disadvantage here. >=20 I concur. The thought of losing Mailman 2.x fills me with dread. =2D-=20 Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12069577.xkLNZX5ndW>