Robert, On Mon, 2007-01-22 at 09:06 -0800, Robert Hudson wrote: > I agree that this doesn't "have" to be done from the ScmBug Daemon and I > could write a completely separate Daemon to allow the operation to be > done. However I was trying not to have multiple Daemons running on a > machine (Purely from a maintenance side of things).
I am saying that NO DAEMON would be needed at all. Just have your hook do what it's supposed to do on the machine that's hosting the repository. Is there a particular reason you want your script to execute on the machine running the daemon instead of the machine hosting the repository ? This isn't clear to me yet. > I was just suggesting the possibility of a generic run command interface > on the ScmBug Daemon to allow an open interface for such an operation. I am not against doing it. I am still trying to understand the benefit of Scmbug. e.g. you could have achieved the same effect by running rshd or sshd on the server and executing scripts there (you still wouldn't have to write an extra daemon). So, were you hoping to do it inside Scmbug because you could have e.g. the list of affected files, or the version number of the update, etc. If not, then wouldn't rshd and sshd offer the same benefit ? Unless I see some benefit Scmbug would add, then I don't see why it should be supported. _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
