Hi all,

I've just set up the cvs area on SourceForge. If you'd like
to try it all out, here's the info:


Ten steps to a working build of dqsd from SourceForge:

(1) Make sure you're using Windows 2000 or better.
(2) Install cygwin from http://cygwin.com/setup.exe
(3) Install Microsoft Visual C++ 6.0
(4) Install NSIS - http://http://www.nullsoft.com/free/nsis/
(5) Make sure that MSVC and NSIS are on your path (I use
Control Panel/System Properties/Environment Variables)
(6) From your cygwin prompt, type the following to checkout:

cd ~
cvs -d:pserver:anonymous@...:/cvsroot/dqsd login
cvs -d:pserver:anonymous@...:/cvsroot/dqsd co
dqsd

(7) And whenever you want to get the latest:

cd ~/dqsd
cvs update -dP

(8) Type the following to build:

cd ~/dqsd
src/build.cmd

(9) In the end, you should get a dqsd/dqsd.exe.
(10) To go back to pristine sources, run src/clean.cmd


The above is for read-only access to the sources. For
writable access, you'll need a sourceforge account, and
Dave will have to grant proper permissions to your account.


----

Ground rules for checkins into CVS:


* If you want to merge in some changes, just let Dave know
which SourceForge account needs cvs write access. Access
is no problem if you're going to contribute; just don't
abuse it.

* When you do commit a change, please let Dave know.

* If you're going to do major rearrangment, broadcast your
intent on groups.yahoo.com/group/dqsdd ahead of time.

* If you're adding novel functionality, please consider
including an option for preferences.js to turn it off.
Also please consider making the default "off" until
it's completely tested and polished.

* Small changes should have small diffs. Please do not use
a wysiwig HTML editor that will introduce diffs on every
line, or your checkin will be backed out.

* In the code, please mimic the prevailing convention for
tabbing and spacing:

1. No tab characters in code please. Use spaces instead.
(The exception is where tabs have semantics of course)
Code should be indented 2 spaces per level.

2. Please, no space characters after a ( or before a ).

3. Curlies for a {multiline block} should be on their own
line and unindented (just their contents are indented).

* Also please mimic the prevailing convention for packaging:

1. Sources should be included in the distribution itself
since this is the easiest way to conform to the GPL.
So all source files should be listed in "search.nsi";
i.e., you shouldn't need cvs to get a working build.

2. Please keep "build.cmd" working. In particular this
means that DQSDTools.mak needs to be kept up to date.
Also, any files that are automatically generated by
the build shuld be deleted by "clean.cmd".

3. Keep new sources, except for those that are being used
at runtime, underneath src/.

* Keep in mind that you're editing other people's code and that
other people will edit your stuff. Please don't be offended
if your code is changed or even disabled. Be nice!

* Dave may decide to turn your access off if things become
unmanagable, or if you don't make checkins for a while.

----

Cheers,

David