Didn't mean to cause trouble - my thought was to make it easier, via a miniscule amount of documentation, for people to transition without getting burnt. After all, since cvsnt is active etc, it would be good to transition everyone off tired old cvs and onto shiny new cvsnt.
I guess I'd say that it would be nice if the description of the cvsnt package made it clear that it *is* a drop-in replacement for the cvs package for *clients*, but that for servers some minimal configuration is required; and a brief /usr/share/doc/cvsnt/README.server saying what needs to be done so repositories in arbitrary locations will work. --Barak. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]