Cinelerra SVN - accessing the SVN

The source code of Cinelerra-CV is available from a Subversion repository.
Subversion is available from Tigris.org, but most likely your distribution has prebuilt packages.
Complete documentation of Subversion is available here.

Checking out a read-only working copy

To check out the most up-to-date version, use this command:

svn checkout svn://svn.skolelinux.org/cinelerra/trunk/hvirtual

This will create a directory hvirtual that contains the working copy. It requires ~170MB disk space.
You can modify this working copy, if you want to (e.g. if you fix a problem), but you cannot check your modifications back in. Developers, see below.

Once you have checked out, you probably will need to run ./autogen.sh in the hvirtual directory to generate the ./configure file and that sorta thing. Most of the missing dependencies should be listed after running ./configure, (and the rest can be somewhat worked out from the compile error message you get.)

If you want to check out an older version, use this command:

svn checkout svn://svn.skolelinux.org/cinelerra/tags/r1_2_2-last/hvirtual

You need to checkout only once. If you want to bring an outdated working copy up-to-date, use this command:

cd hvirtual
svn update

Web based views of SVN.

I know, you're on holidays at a kiosk machine, and are amping to see if any changes have occured in the community version of your favourite video editing software, but only wish you had console access to run 'svn log', No?? Well if so, then have we've got the tools for you! You can actually see a nicely integrated view of the commits or the boring websvn view to actually see the files themselves.

Subversion for Developers

To get the head version use this:

svn checkout svn+ssh://j6t@svn.skolelinux.org/repos/cinelerra/trunk/hvirtual
You need an ssh account on user.skolelinux.org for this. Substitute your login in place of j6t.

NOTE: You may have to type your password more than once, since svn+ssh opens more than one connection. If you see the Password: prompt again two times, it is not necessarily because you typed the wrong password.

In the following, it is assumed that you are inside the top-level directory of the working copy (which is named hvirtual).
Now you can make modifications. When you are done, you first have to make sure your working copy is up-to-date:

svn update

This merges the latest version from the repository into your working copy. You will not be able to commit if there were conflicts. Resolve them first in the code and notify subversion that you have done so:

svn resolve foo.C

(Note that you have to explicitly name the files whose conflicts you have resolved.)
Now do a final check that you are not going to commit unwanted remnants like debugging printfs:

svn diff

Now you are ready to commit:

svn commit

A word about commits

Please solve only one problem per commit. Don't mix unrelated problems in one commit, if possible. If you have solved more than one problem in your working copy, you can create copies of your working copy, then revert some of the changes in one of the copies and commit from there, then update the other copies.

Please make your commit messages descriptive.
Be verbose.

Please be careful that your commit covers everything that belongs to the solution of the problem, if at all possible, so that you don't have to follow-up another commit. Use svn diff. Please do not commit cleanups of any kind. (Since this makes merging upstream versions much more difficult.)