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

Re: "Local" properties? svn:externals

From: Bryan Donlan <bdonlan_at_gmail.com>
Date: 2004-07-17 16:01:49 CEST

On Sat, 17 Jul 2004 03:35:07 -0700, IxokaI <ixokai@gmail.com> wrote:
> Hello all.
> I want to know if its possible to set a property, specifically
> svn:externals, in my working copy and have it _not_ ever get sent to
> the repository.
> Let me describe my repository layout to explain why:
> /trunk/env/Python/
> This is a Python installation. Its in the "env"ironment section
> because it is part of the basis of what makes up the customer's
> environment, along with plugins and SQL scripts that are also stored
> in subdirectories of /trunk/env/.
> /trunk/py/apt
> This is our primary Python source code, where most everything goes.
> /site/(site-name)/
> Site/customer specific information goes here. Specifically of
> interest is /site/(site-name)/config, which contains various key files
> that configure the system. We very much want them in version control.
> Our working copy would end up looking something like:
> C:\Python\ <-- /trunk/env/Python
> C:\Python\apt\ <-- /trunk/py/apt
> C:\Python\apt\config\ <--- /site/(site-name)/config
> That's easily do-able by just setting a couple svn:externals -- but
> then everyone would get those.
> Now, in reality we wont be serving sites from trunk, but from release
> branches and such, but in development and testing we often need to
> evaluate stuff like above. I'd like to locally constrct a working copy
> to work on by setting some properties then somehow preventing them
> from ever being committed.
> Can this be done?

You could check out additional working copies as unversioned objects:
svn co (url)/trunk/env/Python
cd Python
svn co (url)/trunk/py/apt
cd apt
svn co (url)/site/(site-name)/config

You would have to update them seperately though:

cd c:\Python
svn up c:\Python c:\Python\apt c:\Python\apt\config

Or if there's a /trunk/env/Python/apt and /trunk/py/apt/config (either
empty or maybe with template data), you could use svn switch in there
to move it to a different URL in the same working copy.

svn co (url)/trunk/env/Python
cd Python\apt
svn switch (url)/trunk/py/apt
cd config
svn switch (url)/site/(site-name)/config

Then you can do commits and updates in one operation:
svn up c:\Python

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 17 16:02:05 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.