On Mon, 10 Jul 2017 15:41:04 +0200 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? > Yes, the warning would be a repoman check for version bumps, etc... What he is talking about, is OT, and I want to automate with a buildbot instance that can do automated testing for all python pkgs (to start with) that have tests enabled in the ebuild. I am also planning to help with automatic version bumps for those pkgs as well. If not committed straight to the tree, then emailed as a patch to the maintainers, perhaps in a pending repo/branch, bugzilla... TBD. Oh, and I want to connect as many arch specific workers to it as well. That should ease ebuild bumps, PYTHON_COMPAT and keywording maintainence. Once in place and operational, it should give the groundwork to add other pkg types, not just python based pkgs. -- Brian Dolbec <dolsen>
pgpN7g2ENsI6V.pgp
Description: OpenPGP digital signature
