Paul Coddington wrote:
> * The problem of how to copy a project without including the .SVN
> folders, for example, detaching the project from source code control
> for XCopy distribution and installation. At this time, the project
> must be copied to an intermediate folder and custom scripts must be
> written to delete the .SVN folders.
That one is easily solved with the svn export command
> * The problem that a number of command line utilities and developer
> editors performing bulk search and replace operations will corrupt
> the .SVN folder content (as being hidden does not prevent them from
> being acted upon and many tools have no option to avoid acting on
> hidden files and folders). For example, global removal of comments
> from SQL Server scripts on *.* in a folder tree also modifies
> reference copies in the .SVN folder. Specifying individual
> extensions solves the issue, but there are a number of individual
> extensions to take care of one at a time, increasing the risk of
> error or ommission.
Hmm. No easy solution here.
> * The problem that some tools, such as VS.NET do not like having .SVN
> folders in the project tree. (Rather than see this as a bug, one
> should also ask 'why would I want my .SVN folders to be published on
> my webserver in the first place?'). This way, everyone can use
> '.SVN', without resorting to unreasonable workarounds or using '_svn'
> and being incompatible with others.
I believe there are changes coming which will make the .svn folder name
a run-time rather than a compile-time choice.
> Another suggestion: it would be nice to be able to check out an
> entire repository and have an option to automatically obtain the root
> or a named branch (that is, said information is stripped from URL
> automatically).
I don't understand this request.
> TortoiseSVN seems to operate on the assumption that
> you do not have a 'trunk/branches/tags' structure in your working
> folders, but rather you 'switch' a single project folder between
> them. However, this means you can not check out an entire repository
> in one hit, but rather must do it bit by bit, otherwise you end up
> with the 'trunk/branches/tags' folders in your working folder tree.
What makes you think you can't do this already in TSVN? You can check
out any folder URL you want to. We don't recommend checking out the root
because if your project has 100 tags, every single one will be checked
out and you end up with a 100x size working copy. But it is still your
choice. Most people just check out /trunk or maybe /branches/version_x.xx
Simon
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Sep 16 12:22:02 2005