[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Playing the KDE CVS roulette
From:       Bryce Nesbitt <bryce () obviously ! com>
Date:       2001-12-26 13:50:30
[Download RAW message or body]

Developers;

Almost every time I update cvs, dozens of files have changed.  Often if I update
twice in a row, files will have changed.

	-> This is good.  Many people are developing KDE. <-

But this is a nightmare when trying to get a stable version to compile.  It seems that no matter
when I update I catch some project in a halfway working state.  My usual process is
something like this:

	cvs update -A -d -P
	gmake
	cd to broken directory
	cvs update -A -d -P	(every few hours until something changes)
	gmake
	repeat

I often have to make clean and recompile from scratch.  It sometimes takes days to
get back to a working KDE3 after starting to update.  I suspect many developers are
NOT running the current version, they are running a snapshot with just their changes.

Is there a better way?  Could there be a quiet period each 24 hours where developers are
expected to check in only compile fixes?  An extension to CVS to make multi-file checkins
atomic?  Another solution?   Your ideas?

		-Bryce
[prev in list] [next in list] [prev in thread] [next in thread]