|As to the second question -- about obtaining the current contents of the Rochester CVS.
The page http://devel.webwork.rochester.edu/twiki/bin/view/Webwork/WeBWorKCVSReadOnly describes how to set up a "read only" link to the Rochester CVS.
Once set up, a one line command will update the contents your local
collection with the changes that have been collected into the Rochester
repository. (Any changes you have made will not be affected.)
I find it convenient to make an alias called
wwcvs for the line
wwcvs update -A -d
will obtain all of the latest improvements including any new directories (that's the -d flag)
More info on the cvs command can be obtained by typing
The original checkout operation is similiar, but the command is longer,
since you need to specify the repository which you want to check out.
See the page above for details.
For the rochester problems you'll want to use "rochester" for the repository name and
"rochester_problib" for the module_name. ( See http://devel.webwork.rochester.edu/twiki/bin/view/Webwork/WeBWorKCVS
) (You can also use the cvs to obtain the latest versions of the
WeBWorK2 system using "system" as the repository name and
"webwork-modperl" as the module_name. ) Similar access to the other
problem libraries can be arranged if that is desirable.
As to the first question. WeBWorK2 allows you to create a course using
an existing course as a template. That might help with creating a
number of similar courses.
The other solution is to create unix scripts that help automate the
upkeep and synchronization of the various courses. We've not needed to
do a lot of that at
Rochester, but John Jones at Arizona State and Bill Ziemer and Cal
State Long Beach
have more extensive experience managing many similar courses and may
have some scripts that you could use as models for your situation.
<| Post or View Comments |>