On Jun 13, 2006, at 18:08, Matthew Kidd wrote:
>>> The place I am getting confused is right after the "svnadmin
>>> create /path/to/repos" that creates the central repository. I don't
>>> want that. I want separate repositories for each project that we
>>> have resulting in a directory structure like below:
>>>
>>> projectA
>>> /trunk
>>> /branches
>>> /tags
>>> projectB
>>> /trunk
>>> /branches
>>> /tags
>>> projectC
>>> /trunk
>>> /branches
>>> /tags
>>> .....etc
>>>
>>> Do I need to create central repositories for each project? If so
>>> how do the directories created via the "svnadmin create" factor in
>>> to the directory structure I want above?
>>
>> Yes, if you want separate repositories (and separate repository
>> revision numbers) for each project, you would "svnadmin create" a
>> repository for each project:
>>
>> svnadmin create /path/to/projectA
>> svnadmin create /path/to/projectB
>> svnadmin create /path/to/projectC
>>
>> And you could then create the empty directory structure in each:
>>
>> svn mkdir \
>> file:///path/to/projectA/trunk \
>> file:///path/to/projectA/branches \
>> file:///path/to/projectA/tags \
>> -m "Creating empty trunk / branches / tags directories in projectA"
>>
>> And so on for the other projects.
>
> I attempted your suggestions and got a few errors. When attempting
> "svn mkdir" as you typed I got two different errors:
>
> 155007 '.' is not a working copy
> 170000 Unrecognized URL scheme ' '
>
> The first one confuses me but not as much as the second since I
> typed exactly what you had there. I tried the command both in the
> newly created repository and in my home directory. Anyone have any
> explanation for these errors?
>
> Also, if I created a tmp directory with a branches, tags, and trunk
> directory structure with our project structure, excluding the
> project root folder (i.e. /ProjectA/sudirectorieshere, thus minus
> the ProjectA), in the trunk directory, would importing that tmp
> directory accomplish what I'm trying to do?
I'm not sure what those errors are about either. Since I'm supplying
complete repository URLs to "svn mkdir," it doesn't require or make
use of a working copy, so it shouldn't complain about the working
directory not being one. Also not sure about the second error.
Yes, creating the directory structure locally and importing it would
have the same effect, and this is in fact what I usually end up
doing, because I didn't know before trying it out to send you the
above (or else I forgot) that you can give "svn mkdir" multiple URLs
to create in a single revision.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 13 22:55:16 2006