CVS

From K-3D

Overview

The K-3D 0.6 source code is maintained using a CVS repository hosted by SourceForge. Please read the detailed SourceForge instructions for CVS access, including developer access. You may also Browse CVS online. Developers will want to become familiar with the official CVS Manual.

Getting the Development (0.7) Source Tree

See Subversion for instructions on how to obtain the K-3D development tree.

Getting the Stable (0.6) Source Tree

$ cvs -d:pserver:anonymous@k3d.cvs.sourceforge.net:/cvsroot/k3d login
$ cvs -z3 -d:pserver:anonymous@k3d.cvs.sourceforge.net:/cvsroot/k3d co -r k3d_release_0_6 -d k3d-0.6 k3d

Your new copy of the source tree will be in the "k3d-0.6" directory. We strongly recommend you use "k3d-0.6" as your working directory, to avoid confusion if you decide to work with the development tree.

Staying Up-To-Date

From this point forward, you can update your CVS tree periodically to stay up-to-date with the latest changes. From within the top-level of your source tree, do:

$ cvs -q update -d -P

... and CVS will synchronize with the latest sources. The "-q" option means "work quietly", which makes it easier to see exactly what's changed since your last update. The "-d" option forces the client to retrieve any newly-added directories in the source tree. The "-P" option removes empty directories from the source tree.

Important Note #1

K-3D 0.6 Only! Anytime you synchronize with CVS, you MUST re-run the bootstrap and configure scripts. We get a significant number of support requests from people who "got the latest from CVS and now the build is doing funny things" ... when we hear this, we're going to ask you whether you re-ran bootstrap and configure, so you might as well just save us the trouble!

Important Note #2

Anytime you access anonymous CVS, keep in mind that the anonymous CVS server is synchronized with the developers' CVS server on an approximate six hour interval. That means that you might have to wait for up to six hours to obtain changes that have just been checked-in.

Important Note #3

CVS does not provide transactional semantics - if you are updating your sources from the developer tree at the same time that someone else is checking files in, there is no guarantee that you won't receive some combination of old and new sources. Anytime you've done an update and your build stops working, try doing another update before reporting a problem. And while you're at it, did you re-run bootstrap and configure?

CVS Policy

• Potential developers must submit at least one patch before getting CVS write access.
• Build and run before committing code to the CVS repository.
• During release phase, all developers MUST run the regression test suite and pass all tests before ANY checkin.

Miscellaneous

CVS stores text files unix-style in the repository; it then does a conversion to dos-style on the appropriate architectures. That's why you have to use "-kb" when you add a binary file to the repository, to suppress this behavior.