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

Re: batch scripting to add svn:ignore values to a directory

From: stug23 <pat.podenski_at_gmail.com>
Date: Sun, 15 Nov 2009 00:43:39 -0800 (PST)

My current script looks something like this:

svn propedit svn:ignore --editor-cmd "sleep 2;sed -f script.sed" URL

stug23 wrote:
>
> A fairly common pattern for automation is to script the creation of a
> project (in my case using a Maven archetype), followed by importing the
> project into Subversion. After the project is imported the script would
> then set some svn:ignore values on a specific sub-directory within the
> project source code tree.
>
> All of this should be possible without having to check out the project
> since this is a lights-out batch script to create a project and put it
> into Subversion.
>
> My current sticking point is trying to get propedit to work with a script.
> I tried using sed and could not get past the error "No changes to property
> 'svn:ignore'". I noted that in the past others posted with respect to this
> problem and didn't appear to find a solution.
>
> It does seem a bit peculiar that Subversion doesn't have a simple way to
> automate this. Apparently propset has never been granted the ability to
> remotely set properties due to philosophical issues. Nonetheless, this
> task should be a no-brainer.
>
> Any ideas on how to pull this off would be appreciated.
>
> :handshake:
>

-- 
View this message in context: http://old.nabble.com/batch-scripting-to-add-svn%3Aignore-values-to-a-directory-tp26357390p26357398.html
Sent from the Subversion Users mailing list archive at Nabble.com.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2418093
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-11-15 09:44:54 CET

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.