On Sat, Dec 28, 2019 at 10:05:02AM -0800, Alec Warner wrote: > On Sat, Dec 28, 2019 at 3:43 AM Kent Fredric <[email protected]> wrote: > > > On Sat, 28 Dec 2019 11:35:49 +0000 > > Michael 'veremitz' Everitt <[email protected]> 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
Ah, you found the Achilles heel. It is much easier to postulate on the mailing list, use big words, and then say you just won't do that thing because tools/languages such. Perl though... -- Cheers, Aaron
signature.asc
Description: PGP signature
