On December 14, 2016 2:40:45 PM GMT+01:00, Andrey Utkin <andrey_ut...@fastmail.com> wrote: >On Tue, Dec 13, 2016 at 06:00:25PM -0500, Mike Gilbert wrote: >> Keeping up with the frequent Chromium releases is quite a chore. >> Recently, phajdan.jr has been slacking on the masked dev channel >> updates due a hardware problem, so I have been spending additional >> time on them. >> >> If there are any developers with relatively fast hardware that could >> take on the stable and/or beta channel updates, that would be most >> appreciated. This is also something that could be done by a trusted >> user. >> >> Help with the masked dev channel is also welcome -- especially >testing >> the various USE flags and unbundling libraries. > >Have reasonably powerful amd64 hardware, can try nightly runs. > >Not an affiliated gentoo developer. > >I guess it would be best to make up collectively a tiny git repo with >scripts which do exactly what is needed? > >First of all it could be a set of chromium builds with different use >flags (a set of such configurations needs to be defined), saved as >binary packages, so that all the builds could be tested at once by >unpacking every build, in turn. All build logs must be saved for >review, >and failures should be reported. Makes sense? Ideas? Comments?
I could run this automatically evey night. Inside a set of different chroots which sync against the tree then try to install and package the latest ~amd64 version with a USE combination set per chroot. The resulting build logs can be emailed automatically and binary packages uploaded to a specified location. I also have reasonably fast hardware available. If similar activities would be useful for other packages. That should be possible as well. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
