fredag 12 februari 2021 kl. 09:27:25 UTC+1 skrev lorenznl: > 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-)
I'm thinking along the same lines. The design would be similar to the way you can configure Subversion's password-db/authz-db with a ^/filename to use a file in the repository. The security implications would be more or less the same as using a script in the WC. TSVN already store a hash of an "approved script" that exists in the WC and when the script changes the user will be prompted to approve the new script. Supporting a ^.../ path just means checking out a hidden WC somewhere (%appdata%?) and keeping it updated. This is a reasonable use case for me and I could probably look the code, but I would like to ask for Stefan's confirmation that he would consider merging this in the end before doing a lot of work. For the time being, I'm setting up all our client computers to checkout the script to C:\XXXXX\ and doing an SVN UP using Task Scheduler. That will more or less accomplish the same thing but it would be handy if TSVN could manage it automatically. -- 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/29f02080-7067-45e6-89a1-5341bd197648n%40googlegroups.com.
