From: orbea <orbea@riseup.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] games-emulation/jgemu keywording request
Date: Mon, 11 Sep 2023 13:11:51 -0700 [thread overview]
Message-ID: <20230911131151.1e5be4b6@Akita> (raw)
In-Reply-To: <87a5ts1ov1.fsf@gentoo.org>
On Mon, 11 Sep 2023 20:38:48 +0100
Sam James <sam@gentoo.org> wrote:
> orbea <orbea@riseup.net> writes:
>
> > On Mon, 11 Sep 2023 19:18:45 +0100
> > Sam James <sam@gentoo.org> wrote:
> >
> >> orbea <orbea@riseup.net> writes:
> >>
> >> > Hi,
> >> >
> >> > Several months ago I made this issue for keywording the
> >> > games-emulation/jgemu meta package which is a collection of
> >> > minimal emulators for the command-line games-emulation/jgrf
> >> > frontend with a focus on accuracy.
> >> >
> >>
> >> You've not populated the package list and no arches are CC'd, but
> >> we don't keyword things for no reason either on (very) niche
> >> arches.
> >>
> >> Please select a reasonable set of architectures.
> >>
> >> > https://bugs.gentoo.org/891201
> >>
> >>
> >
> > Apologies, I wasn't aware I needed to do that and in retrospect I
> > should of thought of it. Just to be clear you mean add an issue for
> > each issue and then use them as blockers for the
> > games-emulation/jgemu issue?
>
> No, one bug is okay if you populate the package list field in
> Bugzilla.
>
> Just keep in mind that keywording isn't the same as upstreaam CI
> either and we generally want to only keyword on arches where someone
> is likely to use it.
>
Apologies, I now understand what you meant...
The goal is to hopefully entice real world testers on systems that
jgemu may be used. This is not something a CI would be able to
accomplish.
Do I want independent issues for the dependencies?
next prev parent reply other threads:[~2023-09-11 20:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 17:55 [gentoo-dev] games-emulation/jgemu keywording request orbea
2023-09-11 18:18 ` Sam James
2023-09-11 18:55 ` orbea
2023-09-11 19:38 ` Sam James
2023-09-11 20:11 ` orbea [this message]
2023-09-11 20:21 ` Mike Gilbert
2023-09-11 20:31 ` orbea
2023-09-11 20:40 ` Sam James
2023-09-11 20:54 ` orbea
2023-09-11 20:44 ` Alexey Sokolov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230911131151.1e5be4b6@Akita \
--to=orbea@riseup.net \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox