Re: ares and n64 support

--SeOruPDpzA/fpPyJ
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Le Wed, Jan 14, 2026 at 05:08:51PM +0000, David James a =C3=A9crit :
> The other way to keep everyone happy would be to split the package.
> There could be an ares-legacy package which would be the same as the
> current package (i.e. built against v1, no n64 support) and
> introduce an ares-full package built against v2 with n64 support.
>=20
> Anyone upgrading from the current package would get ares-legacy. We
> could put one of those NEWS things up when people upgrade warning
> people about the split and if their system supports v2 they should
> uninstall ares-legacy and install ares-full.

If the extra work seems reasonable, it looks like the best of both worlds.

In some future Debian release we might switch to ares =E2=86=92 ares-full i=
nstead
of ares =E2=86=92 ares-legacy, and then watch the -legacy package usage slo=
wly fade.

--SeOruPDpzA/fpPyJ
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQSUsdxM90hewW6X7Jhja3j5HOuA2AUCaWfXVgAKCRBja3j5HOuA
2M3AAP4qTGP4tH0LZEUDL3nYd/btwZPUI7+g5IAlH0jYdSDNlwD9ENJRNCGDlkCu
NHRJ04/aAEhBmxsYarPfPr3Wd+mcdgQ=
=qlKw
-----END PGP SIGNATURE-----

--SeOruPDpzA/fpPyJ--