You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Miron Bar-am <mi...@astc-design.com> on 2006/07/28 01:30:28 UTC
Local copy of a directory deleted by 3rd party tool and replaced
with a new directory with the same name
Hi,
I have a local copy of a design. One of the directories is a report
directory. All tools I use generate reports to this directory.
During its run, one of the tools, Spyglass, is creating a sub directory
named 'reports_spyglass', which I've also added to the repository.
During subsequent runs, the Spyglass deletes the 'reports_spyglass'
directory and creates a new directory with the same name,
where all reports are dumped to.
Since the directory was deleted (.svn was removed), Subversion doesn't
see this directory as a local copy anymore and refuses to commit it.
The only workaround I found, is to 'svn rm' the directory before running
Spyglass, and then 'svn add' the directory after the tool
has been run.
Is there a more efficient way that Subversion can handle this kind of
situation? For example, define that the .svn directory for the
'reports_spyglass' directory, will be saved in the parent directory.
Thanks and best regards,
/Miron
--
Miron Bar-am
Electronics Hardware Engineer
Australian Semiconductor Technology Company (ASTC) Pty Ltd
76 Waymouth Street
Adelaide 5000, South Australia
ABN: 18 117 392 784
Tel: +61 8 8231 2782
Mob: +61 431 253 227
Email: miron.baram@astc-design.com
Web: www.astc-design.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Local copy of a directory deleted by 3rd party tool and replaced with a new directory with the same name
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Jul 28, 2006, at 03:30, Miron Bar-am wrote:
> I have a local copy of a design. One of the directories is a report
> directory. All tools I use generate reports to this directory.
> During its run, one of the tools, Spyglass, is creating a sub
> directory named 'reports_spyglass', which I've also added to the
> repository.
>
> During subsequent runs, the Spyglass deletes the 'reports_spyglass'
> directory and creates a new directory with the same name,
> where all reports are dumped to.
>
> Since the directory was deleted (.svn was removed), Subversion
> doesn't see this directory as a local copy anymore and refuses to
> commit it.
> The only workaround I found, is to 'svn rm' the directory before
> running Spyglass, and then 'svn add' the directory after the tool
> has been run.
>
> Is there a more efficient way that Subversion can handle this kind
> of situation? For example, define that the .svn directory for the
> 'reports_spyglass' directory, will be saved in the parent directory.
No; that would be this feature request:
http://subversion.tigris.org/issues/show_bug.cgi?id=707
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Local copy of a directory deleted by 3rd party tool and replaced with a new directory with the same name
Posted by Gavin Lambert <ga...@compacsort.com>.
Quoth Miron Bar-am <ma...@astc-design.com>:
> I have a local copy of a design. One of the directories is a report
> directory. All tools I use generate reports to this
> directory. During its run, one of the tools, Spyglass, is
> creating a sub directory named 'reports_spyglass', which I've also
> added to the repository.
>
> During subsequent runs, the Spyglass deletes the 'reports_spyglass'
> directory and creates a new directory with the same name,
> where all reports are dumped to.
>
> Since the directory was deleted (.svn was removed),
> Subversion doesn't see this directory as a local copy anymore
> and refuses to commit it. The only workaround I found, is to
> 'svn rm' the directory before running Spyglass, and then
> 'svn add' the directory after the tool has been run.
>
> Is there a more efficient way that Subversion can handle this kind of
> situation? For example, define that the .svn directory for
> the 'reports_spyglass' directory, will be saved in the parent
> directory.
If you can reliably execute commands both before and after running
Spyglass, then you can backup the .svn subfolder inside
'reports_spyglass' (and any subfolders as well) prior to running
Spyglass, and then restore it afterwards. As long as the .svn folder is
intact then it will get preserved as a proper working folder and will be
able to calculate diffs of the contents (assuming they're text files).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org