From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Keywordreqs and slacking arch teams
Date: Sat, 28 Dec 2019 10:05:02 -0800 [thread overview]
Message-ID: <CAAr7Pr8U8Bqm1t9xS0ziXdkuDBwDsZMqOcwqk+i9GYuOUYj79Q@mail.gmail.com> (raw)
In-Reply-To: <20191229004254.5c8a3f5f@katipo2.lan>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
On Sat, Dec 28, 2019 at 3:43 AM Kent Fredric <kentnl@gentoo.org> wrote:
> On Sat, 28 Dec 2019 11:35:49 +0000
> Michael 'veremitz' Everitt <gentoo@veremit.xyz> wrote:
>
> > Note: we're nnot acttually talking about replacing portage here, just
> > creating a tool ((((thiink php script web tthingy)) that will do some of
> > the pre-screeninng worrrrk that AT hate (eg.... what kensiington did
> with
> > stable-bbot)
> >
> > * with apologies for keyboard/remote-access lagggg creating typo hell.
>
> But, doing that requires viewing realised copies of ebuilds, which
> requires interpreting eclasses and variable interpolation, which
> requires bash sourcing, which requires a mountain of portage hell.
>
> Yes, sharing the stable-bot logic would probably be fine.
>
> But it doesn't use a database AFAIK, it would likely just be making use
> of the MD5Cache (either directly, or indirectly via portage APIs)
>
> But I won't be volunteering, because I won't touch python.
>
You could of course work together with someone else to write the tool?
-A
[-- Attachment #2: Type: text/html, Size: 1667 bytes --]
next prev parent reply other threads:[~2019-12-28 18:05 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-28 7:09 [gentoo-dev] Keywordreqs and slacking arch teams Michał Górny
2019-12-28 9:27 ` Kent Fredric
2019-12-28 9:35 ` Fabian Groffen
2019-12-28 11:05 ` Kent Fredric
2019-12-28 11:14 ` Michael 'veremitz' Everitt
2019-12-28 11:27 ` Kent Fredric
2019-12-28 11:40 ` James Le Cuirot
2019-12-28 11:44 ` Kent Fredric
2019-12-28 11:32 ` Kent Fredric
2019-12-28 11:35 ` Michael 'veremitz' Everitt
2019-12-28 11:42 ` Kent Fredric
2019-12-28 18:05 ` Alec Warner [this message]
2019-12-29 2:19 ` Aaron Bauman
2019-12-29 5:09 ` Kent Fredric
2019-12-30 1:45 ` A Schenck
2020-01-02 20:32 ` Rolf Eike Beer
2020-01-02 23:25 ` Mike Pagano
2020-01-02 23:35 ` Rolf Eike Beer
2020-01-03 0:19 ` Michael 'veremitz' Everitt
2020-01-03 2:40 ` Aaron Bauman
2020-01-03 10:00 ` Rolf Eike Beer
2020-01-04 11:09 ` Rolf Eike Beer
2020-01-04 11:25 ` Michael 'veremitz' Everitt
2020-01-04 13:35 ` Rolf Eike Beer
2020-01-03 14:37 ` [gentoo-dev] Vanilla sources Michael Orlitzky
2020-01-03 14:40 ` Toralf Förster
2020-01-03 14:41 ` Michael Orlitzky
2020-01-03 14:46 ` Rich Freeman
2020-01-03 14:48 ` Toralf Förster
2020-01-03 22:32 ` Michael 'veremitz' Everitt
2020-01-04 7:38 ` Hanno Böck
2020-01-04 18:39 ` William Hubbs
2020-01-04 18:41 ` Michał Górny
2020-01-07 8:52 ` Hanno Böck
2020-01-03 14:52 ` Michael Orlitzky
2020-01-03 14:55 ` Michael Orlitzky
2020-01-03 16:28 ` Aaron Bauman
2020-01-04 11:01 ` Rich Freeman
2020-01-04 11:42 ` Roy Bamford
2020-01-04 12:54 ` Rich Freeman
2020-01-04 13:08 ` Roy Bamford
2020-01-04 13:43 ` Thomas Deutschmann
2020-01-05 10:34 ` Roy Bamford
2020-01-04 20:13 ` Christopher Head
2020-01-04 20:39 ` Rich Freeman
2020-01-04 13:47 ` Thomas Deutschmann
2020-01-04 18:41 ` William Hubbs
2020-01-04 18:42 ` Michał Górny
2020-01-04 19:13 ` Rolf Eike Beer
2020-01-05 16:41 ` Michael Orlitzky
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=CAAr7Pr8U8Bqm1t9xS0ziXdkuDBwDsZMqOcwqk+i9GYuOUYj79Q@mail.gmail.com \
--to=antarus@gentoo.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