CVS Is a Pain in the CV-ASS
I dont know how many of you work with CVS but it is a useful tool to maintain document history and work in a multi-developer domain. When it works right.
My trouble began when I started reorganizing the directory structure of the Usability.KDE.org website. You cant really “move” stuff, so in order to have that effect, you have to copy the directory, add and commit the directory, update your links then delete the old directory. One thing to note: be sure to rm -rf the CVS directory when you “move” the directory. Thats an easy way to mess up your local module and become utterly confused.
I never really used CVS this much before working on this project. The extent of my experience was updating a module in the FreeBSD ports tree to get updated source. I never had to make changes or add and commit anything so these were all new things to me. KDE has a pretty nice CVS interface called Cervisia which is very easy to use and gives a lot of direction on how to do things (e.g. it tells you after adding/deleting something from CVS you have to then commit it). It didnt really prevent my bad CVS day but eventually (with the help of Frans Englich) I got everything straightened out.
Word to the wise: if youre having problems with CVS (especially adding and commiting), the easiest thing to do is to save your changes outside the repository, delete the local module, re-update and start again.
seele :: Sep.24.2004 :: General, KDE/Kubuntu, Work :: 1 Comment »
I can’t stand CVS.