ferringb

Note also, there seems to be duplicative repos.conf settings; see https://dev.gentoo.org/~zmedico/portage/doc/man/portage.5.html . Note `clone-depth` and `sync-depth`. @mgorny any clue why there is two of these? It strikes me sync-depth ought...

Tracing that code, there's stuff it's doing that feels "poke the cpython guts and piss of the bear". My thought is to drop it out since the usage is AFAIK...

If an API key is required, that endpoint should be 401 (auth denied), not 400 (bad request). My rough notions here: * If it's 401, the error we show should...

It's been a while, but isn't there a repo wide check that does distfile collision check? Either way- what's the main take away here in regards to what should be...

/CC @thesamesam , @ulm , @arthurzam

My bad; I didn't check pre-existing tickets, but I should have. I'm fine w/ whatever, as long as it's tightly defined akin to what I'm suggesting. To wit- one reason...

> Not sure if I understand this correctly. Where would `__QA_ECLASS_DIRECTIVE__` be defined? Not as a variable in the eclass, I hope? (Because starting with `__`, it is a name...

I can live with that, although `__.*__` I tend to lean towards just to keep ebuilds and eclasses out of intersecting the inline metadata. So: bikeshedding. is QA_DIRECTIVES acceptable? Also:...

Inline comments are superior in fidelity and 'better'. They however forces a bash parse for all QA checks even if the check suite is strictly metadata scope and higher, which...

Also: if folks think it's better to just do `# pkgcheck-QA: blah blah blah`, that's an option. My concern is that some rewrites i'm doing on pkgcheck are going to...