On Sun, 9 Apr 2017 15:20:02 -0700 Brian Dolbec <[email protected]> wrote: > > This could be partially automated using buildbot. The easiest would > be for pkgs containing working test suites. Those that pass could be > auto-enabled with that python with ~arch keywords. I think if a > stable pkg is to be added the new python, it should be via a revision > bump and ~arch'ing the keywords. But we could enforce the bot to > rev-bump all ebuilds just as easily.
If the package failed, all that would need to be done kinda like now is a given variable modified in the ebuild. Just marking what ever it did not work with. As mentioned that could be done via my ebuild-batcher[1], though same functionality is easily replicated. I also have an ebuild-bumper[2], that could be made more advanced. I am aware of ebump, but ebuild-bumper is a bit different. It works with sets of ebuilds for bumps and cleaning. It can do individual as well but so can ebump. I plan to further automate ebuild-bumper with something that tracks upstream releases and attempts to automate bumps. Though even running it manually is not cumbersome. Just prefer zero day as much as possible. 1. https://github.com/Obsidian-StudiosInc/ebuild-batcher 2. https://github.com/Obsidian-StudiosInc/ebuild-bumper -- William L. Thomson Jr.
pgp_JhiFSjrcx.pgp
Description: OpenPGP digital signature
