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

Re: Initial Layout Questions

From: Brian Mathis <bmathis_at_directedge.com>
Date: 2004-02-11 06:27:22 CET

A better/other way for you to do an import would be to copy the whole
file tree to a temp working dir, then delete all the stuff you don't
want in svn from the temp copy. Import that tree, then check it out
back into your production dir.

Once you're done the initial import/checkout, files that are both in svn
and not versioned can live side by side in harmony.

As a side note, I was a little thrown the other day when I did an import
using tortoise and it started asking me what I wanted to delete. It
seems more logical to ask if I want to exclude certain files from
import, instead of delete them.

Bryan Andrews wrote:

>No I don't want to version my output - but I don't want the external DLLs to be deleted either - which is what tortoiseSVN intimated when it asks to exclude them.
>Is there a way to not version these DLLs yet not delete them either? Simply exclude files from the repository yet leave them in the folder?
>Thanks.
>
>
>-----Original Message-----
>From: Kevin Williams [mailto:kevin_w69@hotmail.com]
>Sent: Tuesday, February 10, 2004 3:02 PM
>To: users@subversion.tigris.org
>Subject: RE: Initial Layout Questions
>
>Bryan,
>
>
>
>>"... populate the repository with that layout and with initial project
>>data."
>>
>>
>
>The Daily Use Guide for TortoiseSVN suggests:
>--------------8<----- snip
>------8<---------------------------------------------------
>Before you import your project into a repository you should:
>
> 1.
>
> Remove all files which are not needed to build the project (temporary
>files, files which are generated by a compiler e.g. *.obj, compiled
>binaries, ...)
> 2.
>
> Organize the files in folders and subfolders. Although it is possible
>to rename/move files later it is highly recommended to get your project's
>structure straight before importing!
>
>--------------8<----- snip
>------8<---------------------------------------------------
>
>
>
>
>>So if I have an existing directory:
>>
>>D:\Projects\MyProject
>>
>>And I import this into http://svnserver/projects/trunk/MyProject
>>
>>Then I try to check it out to the same folder (D:\Projects\MyProject) is
>>this going to cause a problem?
>>
>>
>
>It shouldn't.
>
>
>
>>... can I just check out over the top of the files already sitting there?
>>
>>
>
>Should be OK.
>
>
>>Also I have dlls that live in the bin directory that I may or may not want
>>to check in, but if I don't want to it says its going to delete them - is
>>that my only option?
>>
>>
>
>Do you really want to version the output of your project? Every time you
>compile, you will have a modified working copy, whether you changed the
>source or not. If you're using TortoiseSVN, this behavior is designed into
>the tool, and is done so for your benefit. You have the option of
>deselecting all the items it intends to delete, if you really want to
>version your binary output.
>
>I strongly suggest that you test with some non-essential files until you
>understand what Subversion expects from you and how to use it to your
>greatest benefit.
>
>Hope that helps!
>
>Kevin
>
>_________________________________________________________________
>Let the advanced features & services of MSN Internet Software maximize your
>online time. http://click.atdmt.com/AVE/go/onm00200363ave/direct/01/
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>

-- 
Brian Mathis
http://directedge.com/b/
Received on Wed Feb 11 06:27:49 2004

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

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