On Sun, 04 Aug 2024, Andreas K Huettel wrote:

Step 4: Prepare and publish a migration guide for users.
Right now I assume this will mostly mean "select new profile". However,
I have no clue how portage reacts when $ARCH changes.

Presumably this will also require eselect to be updated (and stable): https://gitweb.gentoo.org/proj/eselect.git/tree/libs/package-manager.bash.in#n70

Any good idea how to handle the transitional situation when old and new
arch keywords exist simultaneously?

Ulrich

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

iQFDBAEBCAAtFiEEtDnZ1O9xIP68rzDbUYgzUIhBXi4FAmawdOQPHHVsbUBnZW50 b28ub3JnAAoJEFGIM1CIQV4uDewIAIHbZAzXErketIsrKZlx7e2ihqp8YZVnnTB2 0zDDOHsHTYa4kqclQEo8Fo/0apJxEsHOAZPWH4V5CV0ycz9DcZ30d9jvlCxyCJG0 oup10F8sd29DjcGfNDBPesN812VVJudzoBoaukMXPKNmbFvjsBSjkL/Am+nMxzMz u6ujPneDZqoD1AzAcyI9IRx/E1+uw3v2HDQqtP+cA4xcq79Tv2KLae7EUXOkExUG 5G9T98Fgjeol88SWrflmbt8cRvivXtQwxM2C5kqKpKYUemJ6m07lw+8b6XYnFeX8 OgkR8Wo52lOYKMe5b6FtFqtSlcNUV6hmLESrgMNGHEQymCRCzq0=
=Q2o1
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)