From: Arthur Zamarin <arthurzam@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Matt Turner <mattst88@gentoo.org>
Cc: Sam James <sam@gentoo.org>, Tim Harder <radhermit@gentoo.org>
Subject: Re: [gentoo-dev] Package stabilization groups
Date: Mon, 17 Jul 2023 19:39:30 +0300 [thread overview]
Message-ID: <78c5a348-060c-c61f-d943-d516c7f78122@gentoo.org> (raw)
In-Reply-To: <CAEdQ38G5fMWY+vtpuMh0HFxViWLjkLzxD6K=qdXky44--rgKTA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 864 bytes --]
On 17/07/2023 16.50, Matt Turner wrote:
> On Sun, Jul 16, 2023 at 2:04 PM Arthur Zamarin <arthurzam@gentoo.org> wrote:
>> Now I'll speak from the point of implementer of `pkgdev bugs`. For me I
>> think both approaches are good, but I would prefer the latter over the
>> former. Nicer syntax, easy cache of all groups, easier to solve the
>> "graph problems" in the tool.
>
> Sounds good to me. Should we have infra create a new git repo for us
> for this purpose?
>
No. I think it should go under normal git repo, and not separate repo. I
see no gains from it being under separate repository, only headache (how
to sync between them).
I think a main index files under
"/metadata/${some_good_name}/${group_name}" would be best.
--
Arthur Zamarin
arthurzam@gentoo.org
Gentoo Linux developer (Python, pkgcore stack, Arch Teams, GURU)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-07-17 16:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 14:57 [gentoo-dev] Package stabilization groups Matt Turner
2023-07-16 15:15 ` Fabian Groffen
2023-07-16 15:29 ` Matt Turner
2023-07-16 18:04 ` Arthur Zamarin
2023-07-16 18:11 ` Ulrich Mueller
2023-07-16 18:13 ` Arthur Zamarin
2023-07-17 13:50 ` Matt Turner
2023-07-17 16:39 ` Arthur Zamarin [this message]
2023-07-18 3:42 ` Oskari Pirhonen
2023-07-17 16:37 ` Sam James
2023-07-17 17:34 ` Arthur Zamarin
2023-07-17 18:14 ` Ionen Wolkens
2023-07-24 13:22 ` Agostino Sarubbo
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=78c5a348-060c-c61f-d943-d516c7f78122@gentoo.org \
--to=arthurzam@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mattst88@gentoo.org \
--cc=radhermit@gentoo.org \
--cc=sam@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