Hi,
> Hmm... Well, it's not entirely my fault, as config files should remain
> in the config directory. I will work around it in the RPM, but this is,
> perhaps, something that should be done upstream.
Agreed that config files should remain in /etc. Why not keep the
default_pref file fully in /e
At 08:20 14 10 03 Tuesday, you wrote:
On Tue, 2003-10-14 at 08:06, Brian
S. Bergin wrote:
> There's always the possibility that the file format may change so
it
> should import the old prefs into a new file if it must be
overwritten
> with the original saved as default_pref.bak.
No, it shouldn't.
On Tue, 2003-10-14 at 08:06, Brian S. Bergin wrote:
> There's always the possibility that the file format may change so it
> should import the old prefs into a new file if it must be overwritten
> with the original saved as default_pref.bak.
No, it shouldn't. Overwriting config files is a bad idea
On Tue, 2003-10-14 at 01:13, Peter Kiem wrote:
> Hi,
>
> I recently upgraded my squirrelmail installation using the
> squirrelmail-1.4.2-0.1.7.x.noarch.rpm on a Red Hat 7.3 system and it
> overwrite my /var/lib/squirrelmail/prefs/default_pref file.
Hmm... Well, it's not entirely my fault, as conf
At 01:13 14 10 03 Tuesday, you wrote:
I recently upgraded my squirrelmail
installation using the
squirrelmail-1.4.2-0.1.7.x.noarch.rpm on a Red Hat 7.3 system and
it
overwrite my /var/lib/squirrelmail/prefs/default_pref file.
I have customised this file to provide better defaults for my new
user
Hi,
I recently upgraded my squirrelmail installation using the
squirrelmail-1.4.2-0.1.7.x.noarch.rpm on a Red Hat 7.3 system and it
overwrite my /var/lib/squirrelmail/prefs/default_pref file.
I have customised this file to provide better defaults for my new users
and had to get it back from backu
