Even if stabilisaton is driven by a reverse dependency, please don't let other arches fall behind in libraries. Is there any reason why we would not stabilise this version for x86 as well?
Not at all. I was assuming (when giving my ack to the other stabilization bug) that it would include all keyworded arches. Albeit I did not really follow up on that. Feel free to go ahead and stabilize x86 and ppc64
Thanks for checking back. By default, new versions are stabilised for arches who already have a stable older version. ppc64 would be a new stable arch for this package; not all arches have to be stabilised, for libraries we typically wait if there is any demand either from an application or user. After stabilisation is finished I would like to clean up old versions; as far as I can see there is no current user of =dev-cpp/ms-gsl-2* in gentoo.git.
Sure, I was also already thinking about dropping the old versions of the ebuild. For reference, this bug also inspired me to finally open a keywording bug for "my usual set" of arches (here arm arm64 and ppc were missing).
x86 done all arches done
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=26d42170078b94640529995563017831075669c2 commit 26d42170078b94640529995563017831075669c2 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2021-02-19 02:09:39 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2021-02-19 02:14:05 +0000 dev-cpp/ms-gsl: Drop 2.0.0 and 2.1.0 Bug: https://bugs.gentoo.org/770694 Package-Manager: Portage-3.0.14, Repoman-3.0.2 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> dev-cpp/ms-gsl/Manifest | 2 -- .../ms-gsl-1.0.0-use_system_catch-636828.patch | 21 ------------- dev-cpp/ms-gsl/ms-gsl-2.0.0.ebuild | 35 ---------------------- dev-cpp/ms-gsl/ms-gsl-2.1.0.ebuild | 35 ---------------------- 4 files changed, 93 deletions(-)
