06-06-2010, 06:56 PM
(06-06-2010, 05:47 PM)Miki800 Wrote: I think the phrases in svn have different meaning then those of clear-case
in clear case I check out a file meaning I am allowed to edit it and I can later check it back in ('check-in') with my new edits back into the global stream
if I 'update' my 'view' of the global 'stream' I can get new edits done by other people
a 'view' is a local copy of the stream of the entire source code which I can edit on my own client side
if I preform a 'rebase' to my view of the stream it forces everyone else to later on preform an update for their view and I can later compare rebases with one-another
do all those things have the same meaning in both clear case and svn?
how can I do a non-reserved check out to your source code?
Hmm...
SVN is a bit different. The SVN system itself is an unreserved checkout model.
It works like this:
Google Code hosts a global copy of the code, splitted in revisions.
Each revision contains the modifications applied to the main source code.
Since it's basically a server-client relationship, you need a SVN client application to be able to checkout the code.
IDE's like Eclipse or NetBeans have available built-in plugins for this. With NetBeans for instance, you need to go to Versioning > Subversion > Checkout and then input the link of the main repository (for JPCSP, you can checkout a read-only copy from the link in http://code.google.com/p/jpcsp/source/checkout ).
Then, a copy of the code will be sent to you, so you can compile it locally. Any changes you do on the client side have to be commited to the server, which only users with the right access can do.
Basically, imagine ClearCase's functioning applied to a website or ftp server. One source code in the server -> multiple source code copies for each user.