Christopher Clarke wrote:
> I see your point. The problem I am trying to solve is how to deal with
> files that have been added to the repository and need to exist in each
> working copy but that also need to be different in each working copy.
One approach is to supply a template or default copy under a different
name and a build/setup/install script (or user instructions) to copy the
default file to the expected name if one doesn't already exist.
> The files should have been ignored from the start, but they weren't
> (because either I'm an idiot for adding them, or the situation changed
> since I did -- doesn't matter which).
> The way it works now, I have to email everyone detailed instructions for
> their particular OS and SVN client and, since I use SVN to manage
> development, staging and production servers, I have to carefully
> recreate these steps on each. In the case of production, this will
> increase downtime when I upgrade the site.
> So, yes, I would rather create more work on checkout rather than update
> to keep my system running smoothly. I have to give instructions for
> getting a local copy of the site working anyway -- SVN is just part of
> the picture.
Can't you rename the file instead of deleting it - and set the property
to ignore it when it is copied back to the new name? But unless you are
already running some kind of post-update script locally or can add one,
I think you'll have to manually copy it back from the renamed version
when the update happens.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-15 22:54:01 CEST