Brian Krusic wrote:
> I agree about the forced update issue and went over the requierments
> and ramifications with everyone here.
>
> They are sure that a select area will need a forced/automated update.
>
> I feel that after its done, they will realize that the application
> being developed will not like this sudden update to its modules but
> atleast we can go back revs if needed.
What is the time window? If the application is installed in a specific
location, it should be trivial to have local software monitor a network
accessible timestamp, or even have a cron job do an "svnlook" or "svn info"
based set of commands to determine if the repository has changed relative to
the local download of it. That keeps things client-based, rather than trying
to make the server track who's downloaded what to where and do things about
it.
Basically, the SVN server has *no idea* where the clients downloaded things
to. It's just not part of the system, so it's very difficult to have the
server reach back out and touch everyone who's ever downloaded the stuff.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 17 22:14:03 2006