Hi,

I'm somewhat new to svn also. I got Apache 2 working with it (following 
instructions from the appendix of the SVN book online); after getting that 
set up, now can just create another repository under a common parent folder, 
and can use it immediately. No extra command-line or text file config 
necessary.

Hope this info is helpful and not redundant:

On 8/22/05, S. Isaac Dealey <[EMAIL PROTECTED]> wrote:
> 
> > I was going to be setting it up on my home server - I
> > found this
> > article that seems useful:
> > http://excastle.com/blog/archive/2005/05/31/1048.aspx
> 
> > larry
> 
> Very much so... Thanks Larry,
> 
> Wow... yeah, this is why I have a tough time with most os projects...
> the easiest way to get it working is to use google to find some
> obscure tutorial on a blog that's completley unrelated to /
> unafiliated with the site... and even then the interface is crap...
> TortoiseSVN does a lot of great stuff for you -- only after you've
> spent several minutes in a DOS shell configuring your project with
> cryptic commands -- which for me needs to be done for each new
> project.


You don't actually need any server to start working with it; if your 
repository is under x:\svn\repos1, the URL is file:///x:/svn/repos1/ 
Then create a new repository under x:\svn\repos2 by creating that folder, 
TortoiseSVN context menu, Create repository here.

After getting it set up in apache2 (yeah, bunch of text config file setup at 
first, and command line for the password file), it's now dead simple to add 
new repositories. No extra config necessary, as it was all in the apache 
config, as opposed to svnserve which depends on the specific repository. 


Though it seems that I now hav it running... The problem with not
> seeing the context menu items and tabs they described is that having
> them show up requires that the subversion server wasn't running! (not
> mentioned at all during installation of course) ... You don't just
> install it and then run it either, you install it, spend several
> minutes in obscure configuration between the dos shell and a text
> editor, THEN you install a windows service wrapper for it (that isn't
> mentioned on the Subversion site), configure and run the service and
> finally you have it running in an intuitive manner.


yeah, svnserve seemed like a pain in the neck that would need to be repeated 
for each repository; that's why I went with the apache2 config. Also pain in 
the neck, but less so, more documented in one place and wouldn't need to 
repeat :)


And even then TortoiseSVN doesn't appear to have any built in
> functionality for creating directories within the SVN repository...
> which is the reason I have to spend several minutes with a dos shell
> each time I create a new project, since I want each project to have
> its own directory in the repository.


Try TortoiseSVN's repository browser. can launch from anywhere in Windows 
Explorer, doesn't have to be in the working folder. Once in the repository, 
right-click in the root or in a folder, and can create folder, copy(branch), 
whatever.

So I can just continue to work the way I've been working for the most
> part... My only remaining question at this point is this:
> 
> When I package up my applications for consumption by others, how to I
> include the SVN info? I notice it creates a .svn directory in the
> working directory of the project -- is that all it needs is for that
> directory to be included in the zip (after committing changes) or do I
> need to explicitly export the info for the directory in some way? I
> haven't read through all the docs yet -- I've just been working with
> the hints... But if somebody else already knows, a hint would be
> FABULOUS! :)


> s. isaac dealey 954.522.6080
> new epoch : isn't it time for a change?
> 
> add features without fixtures with
> the onTap open source framework
> 
> http://www.fusiontap.com
> http://coldfusion.sys-con.com/author/4806Dealey.htm
> 
> 
If you're packaging the app, you probably don't want the .svn directories, 
so they get just the code? If you want to *not* include them, then export 
the project (trunk) to another directory (instead of checkout), to get all 
latest files, but not make it a working folder. 

HTH,
- David


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Find out how CFTicket can increase your company's customer support 
efficiency by 100%
http://www.houseoffusion.com/banners/view.cfm?bannerid=49

Message: http://www.houseoffusion.com/lists.cfm/link=i:5:170818
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/5
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:5
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.5
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to