Sparc is another minor arch which is significantly behind on
stabilizations, so we need to open a bug for it similar to the one for
Let's list all possible options:
A. regarding stabilizations:
A1. dilfridge's GLEP  -- let's us stop worrying about ~arch/arch while
leaving keywords in place. However, it's not an option that we can expect to be
finished and ready for use soon, so I say we don't consider it.
A2. dropping everything to ~arch -- we lose current stable keywords, so if
someone wants to restore stable sparc, he will need to start over.
B. regarding the sparc architecture in general:
B1. dropping profiles to dev/exp -- we stop caring about sparc
This has the disadvantage that the depgraph quickly becomes a mess, and
if someone wants to resume it, it's a lot of work.
B2. dropping sparc completely -- Do we want to consider this since we do
not have any dev machines?
Bug has been referenced in the following commit:
Author: Sergei Trofimovich <email@example.com>
AuthorDate: 2017-09-10 19:17:24 +0000
Commit: Sergei Trofimovich <firstname.lastname@example.org>
CommitDate: 2017-09-10 19:17:24 +0000
profiles.desc: move sparc to exp
On 2017-09-10 council@ meeting majority decided
to drop sparc@ from from 'stable' to 'exp' profiles.
That means the following:
- maintainers are free to break dependency tree by removing
- repoman will stop checking for satisfied dependencies
(unless '-e y' is passed)
Signed-off-by: Sergei Trofimovich <email@example.com>
profiles/profiles.desc | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
For the record, the rationale for this mostly involves lack of operational sparc hardware for dev use.
If someone ever wanted to revive sparc on Gentoo, the first task to do is to install the system on our old sparc machine (or get a new one). Ping Infra to bring a rescue environment up; but note that the arch team is responsible for setting up a real system there.