@broadblues
I missed that. I haven't been using it due to the nature of libraries and their symlinks amongst other things. I'm not sure a RollBack would actually work, but I'd assume it keeps the right datestamp when copying. That's also important.
Quote:
I'm not sure how you set up CopyStore for shard objects (which I'm guessing are what you are writing installers for) when the binary name changes. IT makes abackup of existing binaries via the RollBack database, but a renamed binaray is a "new" binary as far as file names etc go.
a bug fix to lib.so.0.1.2.3 where the name stayed the same would work happily, replacing lib.so.0.1.2.3 with lib.so.0.1.2.4 is essentailly a new binary
I haven't been using CopyStore. For now, it's been removing the old version before installing the new one, which also avoids creating a big mess.
If someone wants to keep an old version, they'd need to do a lot more manual work than CopyStore could provide. They need to backup .pc, -config, .la and header files, and not just of that library, but other dependent libraries. Someone interested in keeping older versions will have kept the other archives, at least up until the point that they're satisfied that the newer version is working properly.
Edited by MickJT on 2014/1/12 9:17:48