On 11 Jul 2017 01:41, Kristian Fiskerstrand <k...@gentoo.org> wrote: > > On 07/10/2017 03:35 PM, Kent Fredric wrote: > > On Mon, 10 Jul 2017 13:43:43 +0200 > > Pacho Ramos <pa...@gentoo.org> wrote: > > > >> Yes, but it's similar as the cases when we need to fix our packages > >> to work with a newer library they depend on. In this case it would be > >> even easier as we can have multiple python versions and switch to the > >> newer one for testing while going back to the stable one (if > >> preferred) later. > >> > > > > I'm starting to think we need a collection of QA scripts in a repo > > somewhere, optimized for symlinking into /etc/portage/hooks/install/ > > > > I might've read things too quickly, we're not talking a repoman check here?
Not sure repoman is enough here. But I'm just saying I see a growing number of problems that can only be detected by actually building the package, and can't be done with static analysis. And then, some of those that can be addressed with repoman are annoying to solve with repoman, as you're tying your release cycle to repomans. And what if your check needs external tools? Surely repoman would be a terrible place to put those dependencies > > -- > Kristian Fiskerstrand > OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net > fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 > --
