Igor Peshansky wrote:
... If the user has modified the default configuration,
she most likely knows what she is doing, and probably wouldn't want the
installation to muck with her changes (not even if we could create diffs
This is certainly true.
(On the other hand, having experienced this
On Wed, 10 May 2006, Thomas Wolff wrote:
Igor Peshansky wrote:
... If the user has modified the default configuration, she most
likely knows what she is doing, and probably wouldn't want the
installation to muck with her changes (not even if we could create
diffs
This is certainly
I'm packaging a new release of lftp. The default config file
(/etc/lftp.conf) is slightly different from the one in the previous release.
This raises a problem: how should I determine whether to replace the old
config file? There are at least three approaches, in increasing order of
complexity:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Schulman wrote:
I'm packaging a new release of lftp. The default config file
(/etc/lftp.conf) is slightly different from the one in the previous release.
This raises a problem: how should I determine whether to replace the old
config
On 5/9/06, Max Bowsher wrote:
(3) Compute a checksum of the current /etc/lftp.conf, and compare it to the
checksum of the old default. If they're the same, then the user hasn't
touched the old default so copy the new default in. If they're different,
then prompt the user as in (2). So we
