[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Automatically run script on checkout - Possible feature request?

From: David Ripton <dripton_at_ripton.net>
Date: 2004-09-02 16:27:34 CEST

On 2004.09.01 15:17:56 +0000, Ken Miller wrote:
> I'm wondering if this might not be a feature that would prove useful to
> others. Here's what I'm thinking:
>
> svn propset svn:checkoutscript name-of-script-with-optional-args
> file-or-dir ...
>
> Then, after svn checks out the directory, it inspects the properties for
> the directory and each file contained therin. For each object
> containing the 'checkoutscript' property, svn executes the pointed-to
> scripts in the directory where the property was configured. In my case,
> I have a Makefile which takes care of running the parser generator. So,
> I would do something like this:
>
> svn propset svn:checkoutscrript make .
>
> 'make' would then be executed in the directory where the property was
> set.

> There could be security issues with this solution, since the script
> would be executed as yourself - if you're not careful, you could do some
> serious damage.

Yes, this feature is way too dangerous. Just because I'm willing to
checkout data from someone's repository doesn't mean I'm willing to
run whatever code he wants me to run.

Sure, you can add more layers of permissions, but they might have
bugs. Better to just not add dangerous features that aren't really
needed.

> I think in the meantime I'll have to check in the generated code, but it
> would be nice to be able to manage the code in a cleaner method.

What's too hard about "svn up ; make" ?

-- 
David Ripton    dripton@ripton.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 2 16:27:59 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.