This is the mail archive of the
xconq7@sources.redhat.com
mailing list for the Xconq project.
Re: Game module versioning
- To: Hans Ronne <hronne at pp dot sbbs dot se>
- Subject: Re: Game module versioning
- From: Stan Shebs <shebs at shebs dot cnchost dot com>
- Date: Mon, 06 Nov 2000 06:13:40 -0800
- CC: xconq7 at sourceware dot cygnus dot com
- References: <l03130300b61d2d23c5d9@[212.112.3.239]>
- Reply-To: shebs at shebs dot cnchost dot com
Hans Ronne wrote:
>
> Not sure about version numbers, though. You may also want to remove a
> finished game from the list if it is too similar to a new one, or obsoleted
> in some other way. What do you do then, downgrade the version number? And
> then there is the point you already made about base modules. Things might
> get confusing after a while.
I've thought about this, and it seems highly unlikely that one would want
to remove a finished game from the regular list but still keep it available
in an expanded list. However, the version property is a string, and thus
not restricted to numbers - the situation you describe ever arises, it
would be possible to have versions like "(retired) 3.2", and test for
those.
> Have you considered having two lists in game.dir (or perhaps two separate
> dir files), one with games that are listed by default, and one with the
> rest? Then you could just move games between the two lists, depending on
> whether you want them to be listed or not. No version numbers to worry
> about.
It's more work... :-)
Stan