Nikos, Sharing my own experience: we've been running many CVS snapshots on production servers handling hundreds of thousands of messages daily for about 5 years and never had an issue that could be attributed to unstable code.
I consider CVS as production quality, and I'm pretty sure I'm not the only one. Regards, Alejandro On Mon, Oct 27, 2008 at 10:56 AM, Nikos Balkanas <[EMAIL PROTECTED]>wrote: > Hi, > > I am rather new to the list. I tried to download and compile the latest CVS > source and I got the following error: > > gcc -std=gnu99 -D_REENTRANT=1 -I. -Igw -O6 -s -m64 -D_LARGE_FILES= > -I/usr/include/libxml2 -I/usr/local/include -Wall -Wmissing-prototypes > -Wmissing-declarations -Wnested-externs -Winline -Wformat -Wformat-security > -Wmissing-format-attribute -Wall -I/usr/local/ssl/include -o > wmlscript/wslexer.o -c wmlscript/wslexer.c > wmlscript/wslexer.c:222: warning: no previous prototype for 'ws_yy_lex' > wmlscript/wslexer.c: In function `read_float_from_exp': > wmlscript/wslexer.c:1037: error: invalid operands to binary == > wmlscript/wslexer.c:1038: error: wrong type argument to unary minus > make: *** [wmlscript/wslexer.o] Error 1 > > Any ideas? How safe is it to use cvs source in production? By the looks of > it, it doesn't look tested. > > Another minor request: Daily snapshots do not have any indication of the > date. This could lead to an invalid snapshot if crontab or the server goes > down at the time of the snapshot. > > Thanks, > Nikos Balkanas >
