Bugzilla Bug 132795

The server.cfg in /opt/enemy-territory/etmain is, as far as I know, the usual
place to put things like rcon passwords, and configuration of the various
parameters you want on your server.

During the recent upgrade to 2.60b, we discovered that server.cfg (and the
other .cfg files in there) aren't under CONFIG_PROTECT, so the upgrade wiped
out a bunch of stuff which we had to recreate from an older backup.  I know
that you can specify commandline options in /etc/conf.d/et-ded, but that's very
cumbersome if you're changing more than a few vars.

Anyway, IMO, server.cfg at least should be under CONFIG_PROTECT, and it would
make sense to just do it to *.cfg in that dir.

Honestly, this is *exactly* why there is the "${dir}/etwolf-homedir" creation
during the ebuild phase.  You're supposed to put your server configs there,
where they won't be written over.

That being said, you're the second person I've heard this from today, so I'm
going to add the standard directories to CONFIG_PROTECT, even though it really
is the administrator's job to extend CONFIG_PROTECT to match their
installation.  This is  FIXED in CVS with no revision bump.  Enjoy!

Ah, I had thought that the et-homedir stuff was just so that the server has
somewhere to write temporary files and logs, etc.  Maybe it'd be worth it to
have some einfo lines in the postinstall to encourage users to put their stuff
there?  I suppose it's a moot point since you've already added the
CONFIG_PROTECT stuff anyway.

Regardless, thanks!

-CJ

huh ?  what directories are you going to add to CONFIG_PROTECT ?

None.  I added /opt/enemy-territory/etmain/*.cfg to CONFIG_PROTECT if
USE=dedicated, not any directories.

yeah, except that doesnt work ...

If CONFIG_PROTECT doesn't work out, I'd think it'd just be enough to mention
where to put server files in the postinstall.  I'd have had my stuff in the
et-homedir if I had known that's where it should have gone in the first place.

Bleh... so it doesn't do just files?  I guess I'll have to look into what
webapp-config does, then, since I could have sworn it can protect single files.

Note added... I guess that makes this "fixed" as best as we can, then.