comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado
Home » Public Forums » archive » Re: SVN Question
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend  		Return to the default flat view Create a new topic Submit Reply
Re: SVN Question [message #57527 is a reply to message #57526] Mon, 10 December 2007 09:08 Go to previous messageGo to previous message
Paul Van Delst[1] is currently offline  Paul Van Delst[1]
Messages: 1157
Registered: April 2002
Senior Member
David Fanning wrote:
> Subversion Experts,
>
> I am still struggling to get my subversion database set
> up the way I want it so I can manage it from within
> the Workbench.
>
> I set up a SNVRepository with TortoiseSNV and imported
> a trunk, branches, and tags directory structure.
>
> What I would like to have is under "trunk" the directories
> "coyote", "catalyst", etc. I was able to do this with
> TortoiseSNV, but I am trying to learn how to do this
> under the Workbench. (I'm always thinking about how I
> would teach this to someone else.)
>
> So, with just the trunk, branches, and tags directories in
> my repository, I bring up the SVN Repository view, and I
> right click inside it, and choose Export.

Don't you want "checkout" ? I assume you're creating a new local sandbox. I only use
"export" when I want to package code up for delivery (i.e. I don't want all the ".svn"
subdirs in my tarball... although the --exclude flag in "tar" works for that too).

> The URL of my
> repository shows up, but cannot be changed. It points
> to "trunk". I can export the proper directory with file,
> then I import them back into an IDL project (giving in and
> putting it in the IDL Workspace, as I am too weary to
> do otherwise), etc. But, in my repository, all the files
> are lumped into one big trunk directory.
>
> This is not what I want, as there is a possibility that
> some files in "coyote" should be different in "catalyst", etc.

This statement confuses me. You don't have replicated files in your repository, surely?
E.g. there is only one version of fsc_color.pro that is used by code in both the "coyote"
and "catalyst" directories.

Or do you mean "projects" here?

> Is the answer to do all repository setup with TortioseSNV,
> and just import files from there into the Workbench?

My MO is:
1) Create a sandbox (branch or trunk, depending on the magnitude of changes being made)
2) Modify code
3) Run tests
(repeat 2 and 3 as necessary)
4) Commit changes
(repeat 2-4 as necessary)
5) Merge with trunk (if appropriate).

You should be able to create as many sandboxes as you want, for different projects or
whatever. You should also be able to create "partial" sandboxes. I hardly ever check out
my entire repository. My Fortran95 subdir doesn't need to know about my IDL subdir.

I can't help you with Workbench-related stuff apart from asking "Why is an IDE making it
*harder* for you to do work?" Parts (2) and (3) are where I can see a developer would
benefit from IDE bells, whistles and gongs. But parts (1), (4), and (5) should simply be
passed along to Subversion, no?

cheers,

paulv

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Another Nice Thing
Next Topic: Re: Freezing your printout...

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Nov 30 01:00:31 PST 2025

Total time taken to generate the page: 1.04252 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.7.
Copyright ©2001-2013 FUDforum Bulletin Board Software