Stefan via TortoiseSVN wrote: >first of all: if the script isn't in the WC then what path are you going to >specify? Meaning to make this work you have to make sure that all >users/developers have the script in the very same path. That's not really >practical and will break easily. >And if it's not part of the WC, then you could potentially execute >something you don't really want: just imagine you're checking out an >opensource project which has hook scripts defined with absolute paths. Now >you do something to trigger one of those scrips, but in your case you have >a completely different script in that absolute path...
I was envisioning something managed by TSVN. (A) WC(s) in %AppData%\Roaming\TortoiseSVN for instance where TSVN would check out the required hook scripts (one (sparse) WC per hook URL, one WC using file-externals, ...). Perhaps with Settings/Properties to control how often to check for updates. For new and updated hook scripts TSVN would then inform the user and ask for permission to use the new/updated script (the dialog could even provide a button to view a diff). I'm aware, that is not something easy to design and implement, and surely not on one afternoon 8-) -- Lorenz -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/m2ec2glnh9gcp82vh1ejcrg61ubqokjjga%404ax.com.
