Changing of behavior: How to tell the user?

Dear Mentors, I'm the maintainer of the CVSNT package. This is a better replacement for CVS and just like CVS it can work as server or client. One of the enhancements (on the server side) was replacing the old directory based file locks with a so-called lock server, which handled all the

Re: Changing of behavior: How to tell the user?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Tscharner wrote: Dear Mentors, I'm the maintainer of the CVSNT package. This is a better replacement for CVS and just like CVS it can work as server or client. One of the enhancements (on the server side) was replacing the old

Re: Changing of behavior: How to tell the user?

On Thu, Jul 17, 2008 at 06:14:51PM +0300, Eugene V. Lyubimkin wrote: Andreas Tscharner wrote: Dear Mentors, cvslockd is started every time. So I created a configuration file /etc/defaults/cvsnt where an environment variable defines whether or not the daemon gets started. I figured that

Re: Changing of behavior: How to tell the user?

On 2008-07-17 17:56 +0200, Justin Pryzby wrote: Another option is to create (only if it doesn't exist, and after doing a version number comparison with dpkg --compare-versions to see if this is a version where it should be created) /etc/defaults/cvsnt as a non-conffile configuration file,