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

Re: Export behaving badly

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2005-10-17 09:52:40 CEST

On Sun, 2005-10-16 at 20:30 -0400, Daniel Berlin wrote:
> svn export svn://gcc.gnu.org/svn/trunk/gcc/doc/install.texi gcc
> It creates a file named "gcc" in the current directory, containing the
> contents of install.texi

Seems reasonable: take this file and put it there.

> Fair enough, though different than checkout, which if you could checkout
> a single file, presumably would have put it in gcc

Sure, but only because working copies must have a directory to put .svn
into. If we stored working copy metadata in homedirs, we might check
out individual files as just files.

(All kind of moot; you can't check out individual files at all yet.)

> -bash-3.00$ mkdir gcc
> -bash-3.00$ svn export file:///svn/gcc/trunk/gcc/doc/install.texi gcc
> svn: Can't move 'gcc.2.tmp' to 'gcc': Is a directory
> I *know* it's a directory.
> That's why i gave it to you. To put the file in.
> IMHO, export's extra argument should behave exactly like the one to
> checkout, and effectively copy the file into that path.

Arguing from consistency with checkout is weird, since you can't check
out an indidivual file. You seem to be going from "checking out a
directory would put the directory contents into the specified directory"
to "exporting a file should put the file into the specified directory".

What you're really arguing from, I think, is cp, which special-cases "cp
file dir" for convenience, treating dir/file as the target path rather
than dir itself. I agree that we should probably do the same thing, but
we're hardly being unreasonable or inconsistent. "svn cat
file://.../install.texi > gcc" would fail similarly, because the shell
has no special case like cp does.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 17 09:54:04 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.