cvs -d :pserver:firstname.lastname@example.org/cvsroot/edbrowse co ebsmjs
Everything you want will be in an ebsmjs directory. Type make, then symbolic link from your bin, or make a bash alias, to the executable. Then, when I report a change or fix, do this from inside the ebsmjs directory:
cvs update -d
It updates only the changed files, you type make, and that's it.
Since I'm not really messing with versions or version numbers, there's no harm in this "get the latest" approach.
I should mention that sourceforge would start to frown if thousands of people were using this method of automatic update, but for a group as small as ours, doing an update every now and then, I don't think it's a problem.
If you have to customize the makefile in some way, to get edbrowse to build, move your makefile to makefile.custom, and create a new build command `make -f makefile.custom'. Then, if I update and overwrite the standard makefile, it won't cause you any trouble.