RE: svn export question

I could have them cd up a level and svn export each project directory separately.

        for project in config scripts support
        do
          svn export svn://zinc/$project $project --force
        done

-----Original Message-----
From: Henderson, Michael D

I'm trying to figure out how our O&M people will pull scripts out of the repository to set up the production environment. I'm thinking that I don't want them to do a svn checkout, mostly because I don't want them thinking that it's okay to update scripts there. svn export looks promising, but I receive a warning that worries me.

svn export svn://zinc .
subversion/clients/cmdline/export-cmd.c:77: (apr_err=155000)
svn: Destination directory exists; Please remove the directory or use --force to ovewrite.
subversion/libsvn_client/export.c:287: (apr_err=155000)
svn: '' already exists

Using svn export svn://zinc . --force works, and does what I'd expect it to, so I will document the --force option on our upgrade process.

The worry is the first part of the message, "Destination directory exists; Please remove the directory." I can see our admins doing an "rm -rf ." puzzling over the error and doing a "cd .. && rm -rf *" to fix it.

So, my question is, is there another way to run the svn export command that will produce the same results but avoid that error message? Or, is there a "better" way of using svn to achieve the same results?

Thanks,
Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 20 20:48:09 2004