I didn't dropped any keywords yet but I've been pretty close to that. See http://bugs.gentoo.org/show_bug.cgi?id=81702 for more info.
Congratulations, you just took something that pissed you off personally and threw it up on the dev mailing list for the purpose of attempting to make a point where there is none. Never mind that for well over a week, you joined #gentoo-mips at least 6 hours before any of us in there would even be awake, said only "mips team ping", and then logged off 5 minutes later. You should have at least talked directly to somebody before getting so pissed off. Remember, when *you* want something, *we're* not likely to come track you down.
I think the reason people drop arches is laziness of some arch herds.
Laziness? I can't speak for other herds, but when stuff like this gets thrown on the backburner with respect to mips, it is because most of us don't even come close to working on gentoo full time. And then, each of us has a specific area that we take care of. I, for example, deal pretty much only with X stuff. Most anything else I consider out of bounds since I either don't know how to test a certain package, or I have no way of testing it even if I wanted to, which leads me to the next point...
C'mon people, how hard can it be to see if it builds right on your arch?
So you are suggesting that we should mark something stable if it simply compiles? I really hope you don't apply this lazy method of QA to everything you maintain, else I fear for the users installing those packages. This is the main reason we didn't touch that package, because none of us had the ability to test pppoe. If you had actually made an attempt to talk to one of us when we were awake before running your mouth, you would have known this. In fact, we probably would have just given you permission to remove the keyword assuming that no repoman breakage resulted.
Steve
-- gentoo-dev@gentoo.org mailing list
