On Jan 11, 2008, at 05:57, an0n1m0us_at_gmail.com wrote:
> Thanks for this, it's very helpful. I've printed the first two
> chapters of the book and am RTFMing :) The initial quality of the
> manual is quite impressive!
>
> One statement I can make that might clear up some confusion is that
> I don't care if the names "trunk", "branches" and "tags" are used
> in the repository's internals and theory. I was just hoping to
> ensure the trunk always related to code in the /home/username/ folder.
You can check out a working copy to anywhere you want. Checking out
to the home folder directly might not be the best idea in the world,
but you can certainly do it:
svn checkout url://to/something/in/your/repository $HOME
Working copies are meant to be disposable. They can get wedged or
otherwise into weird states, and the answer if you ask on the mailing
list will often be "delete your working copy and start over." This
could be inconvenient if you find yourself needing to delete your
home folder in order to get back to work.
> However, if my thinking is now correct, code doesn't 'live' in a
> normal file system folder *until* a version is extracted from the
> SVN internals to a folder. Is that correct?
Yes.
> If this is the case, my scenario would need a situation where any
> code checked in to the trunk would automatically be outputted to a
> real folder. If I was to draw up a basic work flow diagram of what
> I am trying to achieve, would you be able to take a look?
You probably don't want to automatically update users' working
copies. Users should be in control of when and if to update their
working copies. The book will explain this, I'm sure.
It sounds like you're maybe not versioning regular source code
projects? What are you versioning?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-11 22:23:34 CET