Ühel kenal päeval, E, 08.05.2017 kell 22:08, kirjutas Mikle Kolyada: > > 08.05.2017 21:55, Andreas K. Huettel пишет: > > Am Montag, 8. Mai 2017, 12:49:32 CEST schrieb Mikle Kolyada: > > > Against. Do not touch things you are not working on, council has > > > already > > > dropped m68k s390 and sh to exp few years ago. Now we have a big > > > mess > > > there and only, while ia64 sparc and co have slow but progress > > > and > > > mature enough stable profiles. > > > > No objections against having many arches, but: > > > > If an arch is keyworded / stable on more packages than that team > > can > > reasonably take care of, that needs to be corrected somehow. > > > > The easiest solution is for the arch team to remove keywords until > > they have a > > reasonable response time again. And if the arch team doesn't do > > that by > > itself, well, ... > > > > Having one-man teams block everybody else hurts Gentoo as a whole. > > > > We have appropriate hardware if people wanna do the work, jut go & > make > things better :), I do not think someone from existing arch teams has > something against that
We do not want to do the work, as the benefit ratio is bordering zero. IA64 is dead hardware. PPC is dead (ppc != ppc64). SPARC, well, I guess Fujitsu is trying, maybe they should provide a modern dev machine :D Lets have the time of those just keeping it alive by semi-automated scripted STABLEREQ fulfilling spend that time on alive hardware instead. Meanwhile I have various stuff sticking around due to lack of handling keyword requests, including stuff that really needs cleaning up to finish things being really fixed. I actually see one person who seems to care about IA64 a but, but looks like no-one is actioning arch testing anymore.
