Should be fairly ready. Waiting for the ebuild freeze to end. -phoen][x-
Created attachment 4436 [details] ut2003-ded.tar.bz2
First of all: Why do you RESO LATE this w/o asking first? Look at the assignee - phoen][x. Look at the reporter - phoen][x. This bug is a note to myself. 1) With that said, i never tag my bugs RESO LATE (a lot of other devs don't do it either). There's a simple reason behind that: When the bug is still open, it's fairly easy to find it on the buglist. Open bugs dont have an entry in the "Result"-column, RESO LATE bugs have an entry there. That makes things a lot more simpler. Besides, these open bugs in component ebuild dont hurt anybody, why should one touch them. You can always say: "Ah XXXX bugs in ebuilds - that are ebuilds which cant go in cause of the freeze". 2) This package is pending. RESO LATE doesnt exaclty fit. As you might now, i had the permission to add ut2003-demo to the tree while we were in the freeze. I'll talk to drobbins again - maybe he'll give me the permission to add this package too. 3) It's not ~nice~ to modify the status of a bug w/o even writing a single line of text. If you have to change the status, at least say WHY you did it. This all could've been avoided. I hereby ask you not to touch my notes again, please. If you have problems with that, drop me a mail and we shall sort it out with seemant. Thanks, -phoen][x-
first of all, down boy dont take it so personal ... with the ~100 e-mails i get a day about bugs, i see 'new-package' and think 'resolve later' its not like i dont like you, its just that sometimes you smell :/
Why do you browse through my buglist anyways? I have 10 open bugs. 3 of them are ebuilds reported by me, assigned to me. 2 of them are testing bugs. 5 bugs remain. FIVE! Maybe you should take a look at http://bugs.gentoo.org/reports.cgi?product=-All-&output=most_doomed&links=1&banner=1 . Fex look at drobbins 188 open bugs and try to sort out a few of 'em. Or do something else, i dont really care. However, i dont really see the point discussing that with you. I wont mention the ut2003-demo-20020925-r1 ebuild which had a quite obvious bug in the benchmarking. Now guess who committed it. It wasnt me. As you said, "down boy". If you want to make yourself useful, fix some ~real~ bugs. with that said, back to work :)
Okay that was too harsh. Sorry for that. Lets end this now. Just ask before closing my bugs in the future, will you? Or drop some "Closing due to fubar" or whatever in there. It's not that i wanted to offend you, but this whole story makes me kinda mad. Maybe we should sort that out with some ut2003 or q3a match? :) Cya on irc, -phoen][x-
you missed the point of this line: dont take it so personal ... with the ~100 e-mails i get a day about bugs, i see 'new-package' and think 'resolve later' the point was, i dont see who reported the bug or who reported it, i just see the subject (new package) and as such just tag it as RESOLVE LATER ... hence all the other comments of this being personal are nullified ;)
oh and i forgot to add ... i dont browse people's bug lists, i browse via the link 'ALL OPEN BUGS'
Will the ut2003 ebuild be taking into account recent patches, any time soon?
yes, I'm looking into patches as we speak
Hello! Thanks for the ebuild, worked great on my x86 stable, PIII 800mhz machine. It'd be a 'good thing' if the ebuild mentiones how to run the server at the end, just for the clueless ones like me (./ucc server). Also, anyone care to write an initscript (if thats the word) for it? so you could /etc/init.d/ut2003-ded start or whatever. Thanks again! -Matt
does this ebuild still work ? greetz
added to cvs ... if someone ever comes up with init scripts ill add em http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo-x86/app-games/ut2003-ded/ut2003-ded-2225.ebuild?rev=1.1&content-type=text/vnd.viewcvs-markup
