> > > 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 > > I'm sorry, but I can think of about a dozen things where my Gentoo time is > spent in a more useful way. > > (With useful being not so much defined with what I personally find fun, but > with > what brings Gentoo and its userbase forward.) > > Prove to me that more than 10 persons are interested in Gentoo on any of sh, > s390, m68k, ia64, sparc.
well I currently have Gentoo up on bunch of arm v5,v6,v7 1 arm64 5 mips 1 mips64 2 ppc 1 ppc64 2 sparc (64bit) bunch of x86 bunch of amd64 and am still playing with 1 sh3 So how many do I count as 1,2,3-12? ;) Silly Notes: While I personally considered IA64 useless shortly after arrival, Intel has just (5/11/17) announced another bump in that family the 9700 Series. SPARC hardware is stilling being sold by both Fujistu and Oracle, e.g. the M12 series released in April, but it is mostly sold to those already invested in it. Looking I also saw updates in January for the SPARC32:LEON4 processor The OpenSPARC.net SPARC64:T1 & T2 seem less active, may just be my lack of google-fu PowerPC is still running along, mostly embedded for the 32bit version, and IBM still likes to sell big iron with 64bit Power processors. SuperH is even having a tiny bit of a renaissance, what with the J-core.org people building a VHDL open source version for FPGA/ASIC Please note: that I am not objecting to having arch keywords on only the base @system packages for the minor archs, hopefully it will save a small mountain of effort. Would it be worthwhile to have an other/minor/general keyword shared among the arches? e.g. have keywords always try their arch keyword first and if it is not present look for other/minor/general keyword? sort of like */~*/-* except if your arch is mentioned use that instead. It could make things easier many packages /should/ not care about which arch it is exactly. I could see it as trying a stable request: 3 arches send yes and dead silence from everybody else... So after a reasonable time mark the 3 that replied and let everyone who did not follow the general keyword until they reply. My current interpretation: amd64 recent desktops/laptops x86 most older desktops/laptops arm most cellphones/tablets arm64 upcoming cellphones/tablets e.g. raspberry pi3. not yet common running 64bit. mips gobs of routers & embedded systems. everything else niche markets <- Hi, I fit in here a lot. Jim McMechan
