On Friday, March 12, 2021 at 12:11:03 PM UTC+1 [email protected] wrote:
> fredag 12 februari 2021 kl. 09:27:25 UTC+1 skrev lorenznl: > >> >> 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-) > > Ok, so that means you have a way to copy files to every users appdata directory. If you can do that, you can also add registry entries for each user. And if you can do that, you can configure the hooks that way. I suggest you read about group policies and use them on your domain control server. Much easier to handle than what you're trying to do now. 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. > how would TSVN keep that updated? Every time the hook script should run? You'll make your users very angry because of that slowdown... > > 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. > I don't think I would want to merge something like this. Sorry. > > 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. > and you could use a group policy on the domain controller to set up the hook script in TSVN as well as your task scheduler entry. -- 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/be4fa73f-94ae-48af-afe6-338cb419d55cn%40googlegroups.com.
