[gentoo-dev] Mass keywording/stabilisation of ebuilds in app-emacs

[gentoo-dev] Mass keywording/stabilisation of ebuilds in app-emacs

[Ulrich Mueller]

[-- Attachment #1: Type: text/plain, Size: 823 bytes --]

Most packages in the app-emacs category have stabilize-allarches in
their metadata because they are arch independent. However, their
keywords don't reflect this and differ from package to package, mostly
for historical reasons.

So, I would like to mass keyword all ebuilds in app-emacs (as far as
stabilize-allarches applies to them) to the intersection of keywords
of their dependencies. Same applies to stabilisation; if an ebuild is
stable on amd64, I would stabilise it on all other arches, as far as
dependencies allow it.

Also, any new package added to app-emacs in future would start out with
the complete set of keywords. (I am aware that this doesn't agree with
the policy as it is documented in the devmanual:
https://devmanual.gentoo.org/keywording/index.html#keywording-new-packages)

Any objections?

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: [gentoo-dev] Mass keywording/stabilisation of ebuilds in app-emacs

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

On Thu, 2019-10-10 at 16:49 +0200, Ulrich Mueller wrote:
> Most packages in the app-emacs category have stabilize-allarches in
> their metadata because they are arch independent. However, their
> keywords don't reflect this and differ from package to package, mostly
> for historical reasons.
> 
> So, I would like to mass keyword all ebuilds in app-emacs (as far as
> stabilize-allarches applies to them) to the intersection of keywords
> of their dependencies. Same applies to stabilisation; if an ebuild is
> stable on amd64, I would stabilise it on all other arches, as far as
> dependencies allow it.
> 
> Also, any new package added to app-emacs in future would start out with
> the complete set of keywords. (I am aware that this doesn't agree with
> the policy as it is documented in the devmanual:
> https://devmanual.gentoo.org/keywording/index.html#keywording-new-packages)
> 
> Any objections?
> 

Wasn't ALLARCHES supposed to be applied only if a previous version had
a stable keyword on the arch in question?  I.e. if it has been tested by
arch team at least once?

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

Re: [gentoo-dev] Mass keywording/stabilisation of ebuilds in app-emacs

[Ulrich Mueller]

[-- Attachment #1: Type: text/plain, Size: 614 bytes --]

>>>>> On Thu, 10 Oct 2019, Michał Górny wrote:

> Wasn't ALLARCHES supposed to be applied only if a previous version had
> a stable keyword on the arch in question? I.e. if it has been tested
> by arch team at least once?

Yes, but the same would apply to most of the elisp code that is shipped
with app-editors/emacs itself, for which I doubt that it gets large
coverage in arch testing.

Either these things are arch independent, then I don't see why they
couldn't have the same keywords as emacs itself. Or they are not,
then they shouldn't have the allarches label in the first place.

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: [gentoo-dev] Mass keywording/stabilisation of ebuilds in app-emacs

[Sergei Trofimovich]

On Thu, 10 Oct 2019 16:49:20 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:

> Most packages in the app-emacs category have stabilize-allarches in
> their metadata because they are arch independent. However, their
> keywords don't reflect this and differ from package to package, mostly
> for historical reasons.
> 
> So, I would like to mass keyword all ebuilds in app-emacs (as far as
> stabilize-allarches applies to them) to the intersection of keywords
> of their dependencies. Same applies to stabilisation; if an ebuild is
> stable on amd64, I would stabilise it on all other arches, as far as
> dependencies allow it.
> 
> Also, any new package added to app-emacs in future would start out with
> the complete set of keywords. (I am aware that this doesn't agree with
> the policy as it is documented in the devmanual:
> https://devmanual.gentoo.org/keywording/index.html#keywording-new-packages)
> 
> Any objections?

None.

-- 

  Sergei