19.10.2014 15:18, cpu memhd пишет: > I was thinking the same thing to use a temp work dir. But at this point, I > just want to add support for symbolic link and empty directory backups. > > So 'freshen' is to be used for automated, multi package updates? Does anyone > actually use this? > > I don't see how this could work since one modified .local config file will > cause the function to abort. And that's after it has possibly deleted many > files, which at this point, will probably render the package broken. This behavior should be fixed - all local files should be copied/merged to new dir, and only then old package should be cleaned and new - copied.
> Therefore is seems, the -f option is intended to be used when you *don't* > make changes to .local files? This doesn't make sense, what kind of system > would this be, one that utilizes an alternative config setup? If someone has > used this option, I'd like to know. It fails only if local file is changed both by user and in new package. If new package version has same local file as earlier - update goes smoothly. > > The -u option, on the other hand does makes sense. -u differs from -f only in handling changed files - -f just fails, -u - asks to merge/replace modified local file. ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
