On Fri, Jan 04, 2008 at 09:34:42AM +0100, Nils Breunese (Lemonbit) wrote: > Jon S. wrote: > > > I kept my old config.pl when it asked if I wanted it replaced. I take > > it the configuration parameters are the same, just the access to them > > from the CGI interface has changed somewhat. > > I always run a diff instead of assuming the config parameters haven't > changed. I advise anyone to do the same. > ...
Old thread I know but I was thinking about the current situation (at least in debian) with config.pl being changed at each upgrade. To make it easier to keep track of local changes, would it make sense to try and keep the distribution config.pl untouched, and as the last line add an if-exists-then-include of a config-local.pl file? Rather than customise config.pl which would now in essense just be a reference for the defaults, local customisations would be put in the config-local.pl file, which would not be overwritten during upgrade. Is there a better way to acheive this? Just a thought. Regards, Dale ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
