Steve Kargl wrote: > > If you want a robust (but probably really slow) algorithm, you > could use the revision number of a file.
I'd really prefer to have something for the whole collection. If it has to check every file, then it will take about as long as doing an update. I want it to be able to decide very quickly on a per-collection basis before updating anything. > Isn't this a monotonically increasing number? The version numbers should monotonically increase. But they don't always do so, in practice. CVS repository managers occasionally have to do damage control that entails deleting deltas. > Would it be possible to compute md5 signatures on a per-file per-collection > basis? The cvsup server would have, for example, src-bin.md5 which > contains a list of all files in the src-bin collection and their > md5 signatures. When a connection is made to the server, the server > sends src-bin.md5 to the client. The client compares the local > src-bin.md5 with the server's src-bin.md5. Any difference would > indicate a file has changed, and the client then requests the > server to send the changed file(s). But comparing checksums only tells you whether the files are (probably) the same or not. It doesn't tell you which one is more up-to-date. John --- John Polstra j...@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
