> I'm trying to understand exactly what you were trying to do.
> Couldn't this conversion be accomplished by adding an extra,
> separate hook in Subversion ? Or was the fundamental need to
> run it on the machine running the Daemon, which could be a
> centralized location that contains a wide configuration of tools ?
I'm actually running a completely separate repository for documents,
It didn't have any links with the Source repository which used Scmbug.
So I had a completely independent post-commit hook. (I then linked into
Scmbug to solve my problem with this additional interface).
> Was an extra "activity" issued ? When was it issued ?
Yes, I created a new activity, hopefully the help file I posted will
clarify?
> I am definitely willing to see your patch!
I've E-mailed the changes to you, see you've already created a tracking
ID
Thanks.
> If there is a generalization that could be derived from this
> work, then definitely I'd be willing to merge it.
Hope that I've managed to make it fairly general.
> For example, do you want to execute the conversion hook only
> for some paths in the repository ? So Scmbug could have an
> "execution_hooks"
> policy that given a matching filename path they can execute a
> binary ?
I have currently handled the rules to if it should be executed
outside of the Daemon and only call the Daemon if it is required to run.
Thanks, Rob
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
