From: Oskari Pirhonen <xxc3ncoredxx@gmail.com>
To: Arthur Zamarin <arthurzam@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, Matt Turner <mattst88@gentoo.org>,
Sam James <sam@gentoo.org>, Tim Harder <radhermit@gentoo.org>,
ionen@gentoo.org
Subject: Re: [gentoo-dev] Package stabilization groups
Date: Mon, 17 Jul 2023 22:42:14 -0500 [thread overview]
Message-ID: <ZLYKFuJ2IOsGYhHw@dj3ntoo> (raw)
In-Reply-To: <78c5a348-060c-c61f-d943-d516c7f78122@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
On Mon, Jul 17, 2023 at 19:39:30 +0300, Arthur Zamarin wrote:
> 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.
>
/metadata/stable-goups/${group_name} perhaps? Then you can adapt Ionen's
example as:
$ cat /path/to/repo/metadata/stable-groups/qt
dev-qt/package
dev-qt/package2
Easy to read, easy to write :)
- Oskari
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-07-18 3:42 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
2023-07-18 3:42 ` Oskari Pirhonen [this message]
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=ZLYKFuJ2IOsGYhHw@dj3ntoo \
--to=xxc3ncoredxx@gmail.com \
--cc=arthurzam@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ionen@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