[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Bug 183089] Review Request: ularn - a text-based roguelike game



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: ularn - a text-based roguelike game


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183089


j w r degoede hhs nl changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
         AssignedTo|bugzilla-sink leemhuis info |j w r degoede hhs nl
OtherBugsDependingO|163776                      |163778
              nThis|                            |




------- Additional Comments From j w r degoede hhs nl  2006-03-15 16:57 EST -------
Since I'm about to request yet another game SIG related review from you I
thought I would return the favor and see if there were still any open review
requests done by you, so here I'am :)

I haven't taken a look, but the sgid games stuff does not make me very happy.
I'll probably write up a patch which as the first thing of main opens the
highscore file, leaves an fd around for the highscore functions to use and then
 drops the games group rights. The only issue which then remains is do we use
the games user / group for stuff like this, or do we create a user per game. I
must say I like the games user idea for simple on file cases, for more complex
stuff like daemons we should use a new user. What do you think? Maybe we should
take this to the list? Anyways I think that whatever we decide we should put
this on the games-SIG wiki page as games-SIG policy.

I'll start a real review tomorrow, as usual with the kinda comments from me its
bedtime over here (I have a daytime job too :)


-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]