Thus said Stephan Beal on Tue, 21 Oct 2014 17:37:03 +0200: > What version does one hope to get from the remote over HTTP? You can > only tell what versions he's copied/pulled (in that it will be at the > top of the RSS feed/timeline), but that doesn't mean he's got that > version checked out or installed.
I think /timeline.rss?tag=release&n=<somelargenumber> (or a custom report as Ron suggested) will be able to provide this information (unless Fossil is installed), but otherwise, I don't see how he can get it. > > But for auto-updates I need some other way, that to check for newer > > versions than the version on the user's machine. Another problem is > > than only the versions tagged as "release" have to be check. > > sounds _very_ much like the "quiet update" thread from a couple weeks > back, in that the functionality would basically be the same: figure > out if there's a newer version or not (i.e. if there's work to be done > or not). It does sound very similar with the exception that there will be no local checkout of the repository. To be able to determine if there is a change that requires auto-update, he will have to know not only how to get information from the remote Fossil, but also which version is currently installed (I assume he already knows this). Thanks, Andy -- TAI64 timestamp: 40000000544689e3 _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
