chicken: (40. BBEdit)
[personal profile] chicken
So I'm learning the version control software, Subversion, after reading what seem like the revelant chapters in the user manual (everything through Chapter 3, "Guided Tour", inclusive), I still cannot figure out how to do some very basic things.

If you are a version control geek, please read on and consider commenting and helping me. Thank you SO much.



1.) How do I check out just one file from the repository? I don't want the entire directory structure, I just want one file.

Why? You might ask. Because I just want to check out and work on ONE damn file, namely index.php. I don't want to wait three minutes for subversion to slowly check out the entire working copy, which includes many, many megabytes (and eventually gigabytes as I add more files) of stuff including image files.

If you know the answer to this, please also point out to me where in the user manual it says how to do this. I am stupid and unable to find it, but I know it is probably possible to do (I hope).

EDIT, 2:53 pm EST: OK, I figured out how to get just one file:

svn cat file:///srv/projects/svn/myProject/myPath/index.php > index.php

BUT, but, how do I get a whole directory? For example, I want myPath/phpScripts/, but not myPath/images/ and not myPath/gfx. Or more complex, I want myPath/phpScripts/*.php, but not myPath/phpScripts/*.jpg. HELP!

2.) Must I really use this whole 'trunk/branches/tags' directory structure? I hate it, because then after I check out a working copy to my web hierarchy, my documents now have 'trunk' in the URL path, which is just nuts. I mean, I can move them out, and delete the 'trunk' dir, but then what happens when I try to 'commit' the files back to the repository? Will it mess up because I changed the directory structure? Can't I please just dispense with 'trunk/' and 'branches/' and 'tags/' altogether?

If not, why not?

Thanks!

P.S., I know I am being grumpy about these things, but they seem really basic to me and I feel like I'm either really stupid, or the documentation is badly written. Don't get me wrong -- I'm excited about how much more powerful Subversion is than RCS, and I can't wait to figure out all this stuff in a command-line environment, so that I can build on that knowledge and go on to learn new things like how to use svn+ssh and use Subversion remotely with svn+ssh. Really, I am excited, just a bit frustrated as well.

Profile

chicken: (Default)
chicken

April 2009

S M T W T F S
   1234
56 78 9 1011
12131415161718
192021 22232425
2627282930  

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags