Re: Renaming config files
On Sat, Feb 27, 2010 at 02:07:19PM +1100, Ben Finney scribbled thusly:
> Ivan Jager <aij+debian@mrph.org> writes:
>
> > What's the proper way to deal with renaming configuration files?
> > I'm working on a new version of hibernate, and right now it
> > simply adds the new config file and leaves the old one lying
> > around, which is less than ideal.
>
> Is it conceptually the same config file at a newer version? Or is it
> conceptually a distinct file?
>
> What are the reasons the user might want the existing file to remain
> after upgrade, versus the reasons another user might want that file to
> go away after upgrade?
It is conceptially the same file. suspend2.conf got renamed to
tuxonice.conf because Software Suspend 2 got renamed to TuxOnIce.
Some of the configuration directives (the ones containing
Suspend2 in their names) got renamed, so I'm a little tempted to
go with Daniel's suggestion and also s/Suspend2/TuxOnIce/,
although I'm hesitant to modify a user-modified config file...
Ivan
Reply to: