Abstract |
CVS is a well known tool, used by most open-source projects --including all(?) BSD variants-- to store code. But it isn't limited to code, only. It can be used to manage configuration files, and/or a web-site. Both are done frequently, both in free/open projects as well as in commercial environments. Tracking a website, with HTML, php, Java and even pictures is possible with CVS, to. Then a CVS client can even be used for (web)publishing:-)
Some consider CVS as the best tool for 'CM' ever; others think CVS is complex and hard to set-up. Last, there are people complaining about CVS' lack of GUI and it's inability to track bugs. The truth is, CVS is available, usable and easy to manage after a short course.
This tutorial is such a course. After a short introduction into CVS, we directly start using CVS. First as user of a client-server environment. Then, as operator/master of such a set-up. We will see how several tricks can be used to enrich a default set-up to a defacto standard environment. Like FreeBSD's and/or sourceforge.net.
As security is important, SSH/SSL and public/private keys can/should be used. We will (and do) that too. And as we are busy, we can even add GUI clients, both for Unix as for windows (yes; bring your Windows-laptop with you, and you _can_ use it!)
Managing CVS is more then installing some tools and know how to use it. Some tricks can be needed to compensate know of CVS. Logging in into the server, gives you super-power by manipulating files directly! You will learn to do that to.Interested in those "repocopy's" FreeBSD is using? The FAQ explains only for what they are used. Here, you can see for your self; and experience them.
To maximize the gain, tricks used in several public available repositories (like FreeBSD, and SourceForge) and of personal origin are used. This gives both commiters of BSD/open projects, as individual users which need (CVS in) a personal environment a leapfrog in their ability to use CVS; and to discuss/set-up CVS for CM.
The tutorial is aimed for both experienced users of CVS, who need/want to know more about how it works; as for users that just need to set-up a (small) CVS repository themselves. Knowledge of programming languages isn't needed; some scripting knowledge is assumed. As is basic understanding of CVS or any other similar tool. Knowledge of CVS, or (software)configuration management can be handy; but isn't needed.
As hands-on and theoretical parts are interleaved; use of a laptop is encouraged. Any BSD (or even a Windows-PC) will do! You should be able to use the commandline and your editor of choice.
Hope to see you soon! |
Authors Description |
Albert has been using FreeBSD as long as the product exists; he started with 386 BSD, indeed on a 386-CPU. That system is still in use, now as a firewall. Albert is a hardcore Unix-user, running FreeBSD whenever possible. "Running Unix isn't a goal by itself", he always says, "but using FreeBSD can often simplify the solution".
Albert has a broad and deep knowledge about computers, ranging from tool-user, SW-developer to SCM-expert.
He likes to share parts of his knowledge, giving presentations and writing articles. An example of the former was given on the EuroBSCON-2002 (about secure syslog). For dutch readers, the latter can be found on http://albert.mietus.nl/read.IT, where he recently started to collect some articles.
Being an expert on Software Configuration Management, he likes CVS. That tool, although it ages, is still going strong. Frequently he is asked to present a crash-course. Especially for EuroBSDCon Albert has a new goal: Extent and compress it to a full --hands on-- tutorial. See the abstract for more info.
|
