public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexey Sokolov <alexey+gentoo@asokolov.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] games-emulation/jgemu keywording request
Date: Mon, 11 Sep 2023 21:44:38 +0100	[thread overview]
Message-ID: <a9e2fc1f-12c8-00fe-562e-fbaf7ea25318@asokolov.org> (raw)
In-Reply-To: <20230911133123.63156dea@Akita>

11.09.2023 21:31, orbea пишет:
> On Mon, 11 Sep 2023 16:21:43 -0400
> Mike Gilbert <floppym@gentoo.org> wrote:
> 
>> On Mon, Sep 11, 2023 at 4:11 PM orbea <orbea@riseup.net> wrote:
>>>
>>> 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.
>>
>> This is not an appropriate use of Gentoo arch testing. We keyword
>> things based on user demand, not to satisfy the urges of upstream
>> developers.
>>
> 
> Its a common occurrence that upstreams refuse to consider distros and
> leave them hanging, but I honestly did not expect the inverse where the
> distro is unwilling while the upstream is....
> 

End users are already able to attempt building any package on any 
architecture by adding that package and its deps to 
/etc/portage/package.accept_keywords as **

Users who wish to contribute as CI to jgemu can do so already. Users who 
do not wish, won't do that even with the keyword.

-- 
Best regards,
Alexey "DarthGandalf" Sokolov



      parent reply	other threads:[~2023-09-11 20:44 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
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 [this message]

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=a9e2fc1f-12c8-00fe-562e-fbaf7ea25318@asokolov.org \
    --to=alexey+gentoo@asokolov.org \
    --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