Manoj Srivastava wrote:
>       And you are sure these games can't deal with no file being
>  present.

No, I didn't try them. Better things to do, really, than play games..

>  Lemme see: can't test xboing anway,  Xlib Error: BadMatch
>  (invalid parameter attributes)/.

Weird. Could you file a bug report? What color depth/x server/etc are you
using? Anyhow:

XBoing - Warning: Cannot open high score file for reading.
XBoing - Warning: Cannot open high score file for writing.

> nighthawk works

Maybe. I don't understand the game.

> xhextris works

Only if you call refusing to save a high score and printing:

xhextris: Can't open high score file.

working. What'd you do, just try to start each of these?

> xgalaga works

Again, you seem to have a different definition of "works" than I:

Trouble opening high scores file '/var/lib/games/xgalaga_scores'
Trouble opening high scores file '/var/lib/games/xgalaga_scores'
Trouble opening high scores file '/var/lib/games/xgalaga_scores'
Couldn't write scores file /var/lib/games/xgalaga_scores

> sail works.

At least it runs. I don't understand the game well enough to get a score.

> tetris works

So it does.

> rpgue works

cannot lock score file-more-
cannot read/write/create score file-more-
sorry, score file is out of order

> maelstrom works.

So it does, but you lose the ability to look at the Maelstrom global high
score list (the default high scores, posted by others, that you can try to
overcome.) This is also true for several of the other games, btw, and yes,
this is an important part of the whole experience of some of the games,
IMHO.

> getting bored trying to find a game that
> fails if the score file don't exist.

Maybe you should look harder, I'm seeing a failure rate of more than 50%.

> Joey> Because, this contravenes the FSSTND! /etc is for configuration
> Joey> files. These are not configuration files.
> 
>       So you decide that these are not config files. If the game
>  can't work without them, it is a configuration file.

If a game cannot work without a file, the file is a config file? So libc6 is 
a config file? I'm sorry, I don't understand your reasoning, or what you're
getting at.

Anyway, NO, these are not configuration files. They are not edited by the
admin to configure the game, ever. They are data files that change. In 
other words, they are "variable data files" (fsstnd section 5). They belong
in /var.

> If the score file is not required, don't create a conffile, for gods
>  sake. conffile == configfile == configuration file. 

If a game cannot work without a file, the file is a config file? So libc6 is
a config file? I'm sorry, I don't understand your reasoning.
 
>       Actually, past experience has lead me to lower my opinion of
>  some people considerably. And I am not alone vis a vis riff raff in
>  the ranks.

I can't understand how you can continue to use people's packages if you have
such a low opinion of them.

>       Inclusding the dos hdimage, the total came to 514K. The dosemu
>  was 458 k.
>
>       3 or 4 mega bytes? where do get that?

I have a 3 mb dos hdimage. It can be any size.

> Apart from dosemu, I get less than 75K.

Which is still about 25% to 50% the size of a typical debian /etc. Not that
I would consider this a large problem, I think the whole size argument is an
unimportant side issue. The point is that these files do not belong in /etc.
Read your fsstnd!

> And if you have not checked, why do you think I should
> treat your arguments with the respect you think you deserve?

See above. Pot. Kettle. Black.

> Joey> I have only one simple question - if this can be answered to my
> Joey> satisfaction, I would have no qualms about moving all conffiles
> Joey> into /etc. That question is: what does this gain us? I don't see
> Joey> an appreciable gain. I see a lot of stuff moved around in a
> Joey> fashion that makes debian even more unlike a standard linux
> Joey> system. I see the developers hobbled by a useless piece of
> Joey> policy. So where's the gain?
> 
>       Change the policy if you believe it hobbles us. I shall not
>  (again) go into why I think all user modifiable config files should
>  be in /etc. I beleive the benefits are huge, and if we are different
>  from other unices, it is because we offer significant bvenefits.

Just point me at wherever you said it before. I'm interested to hear your
arguments.
 
>       Hobbled by policy, forsooth!

Yes, hobbled by policy. We have a nice general method of ensuring that
changes a user makes to files be preserved accross package upgrades, someone
adds a sentance to policy, and we are suddenly prohibited from using it in
many places. I feel constricted by this.

-- 
see shy jo

Reply via email to