-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/14/2010 12:55 PM, Eric wrote: > > > Even if a repository knows what to do and how to do it, how does it know > it is the repository that is supposed to do it? For checkins on what > branches?
I'd guess the same way it knows what its users and their passwords are. Isn't that the purpose of not pushing local configuration unless explicitly asked to do so? > > How does it get out of its chroot jail? > > What does it do if whatever it runs returns an error? > Those are issues for the hook developer, I'd think. Set up a reasonable chroot jail that includes what is necessary. Handle exit codes and perform some reasonable action when one is received. I don't think that anyone is asking for Fossil to hold their hand through every possible contingency or thing that might go wrong, just to offer the capability to extend. > I am not saying that what is asked for is unreasonable, just that it is > not a job for Fossil itself. Fossil should do what it does. If you want > something different for your developers/contributors, write a wrapper > application. If you want something done on a repository server, write an > independent program that reads the repository database at intervals - > scheduled or a polling daemon. > That's certainly an option, however given the general trend toward push rather than pull in many areas, I'm trying to think of ways for Fossil to notify other entities that something has changed rather than requiring extensions to periodically poll the DB, fetch the feed, etc. If embedded scripts aren't that way then so be it, but I still think there should be some means of push notification to external sources. I understand that the sync protocol currently doesn't support such a thing, so I wonder if it might be made to do so in the future, or if there may be some other mechanism by which this could be accomplished? I understand the desire to not introduce unnecessary complexity, so I'm curious as to the simplest thing to do that might make push notification work. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyPu18ACgkQIaMjFWMehWJGsACePh5AUWK+Wc9Xsncd9/yZYfNI NOQAn1ZIwy5FNyBXGAGaDOYQNn6XD95Z =srqp -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
