CVS and SAMBA

[Graeme . Vetterlein]

-----Original Message-----
From: Graeme Vetterlein 
Sent: Thursday, December 21, 2000 1:54 PM
To: address@hidden
Subject: CVS and SAMBA


Hi I'm not on the mailing list so please CC me ... thanks.

I'm setting up a development group's environment in what I expect will
be a increasingly common fashion:

        1 central SUN box holds the JAVA source code in CVS
        Every developer (group dev) as a Unix login account (thus a $HOME)

        Every developer has MS (W2K) desktop

        Every developer maps $HOME to W:

Thus if the log onto unix:

        Private source is in $HOME/src          Public source is
$PROJECT/src
        Private classes is in $HOME/classes     Public class is
$PROJECT/classes

If they stick to the PC:

        Private source is in W:/src             Public source is X:/src
        Private classes is in W:/classes        Public class is X:/classes

Thanks to samba.

So now on my PC I do:

        set CVSROOT=:pserver:myservername:/user/cvsroot

        cvs checkout ....

And all is fine, I can work OK on the PC.

Now I got the UNIX account and have:

        CVSROOT=/user/cvsroot export CVSROOT

        cvs checkout

This fails with 'used a null password ... etc.'  The reason? It's using:

        CVSROOT=:pserver:myservername:/user/cvsroot^M

Which is what it finds in CVS/root in the CWD.  But if I 'fix' this to
CVSROOT=/user/cvsroot then
the PCs won't work.

If I use cvs checkout -d /user/cvsroot it OK, but 1: that's a pain and
2: I aint really doing this it's
being done in the background by emacs.

Any hints on the best way to do this?

As a BTW: I had a lot of grief with the cygnus cvs.exx and forte, the
gnu wincvs cvs.exe is OK ... thought you
might like to know that :-)




-- 
"We cannot put off living until we are ready.  The most salient
characteristic
of life is its coerciveness; it is always urgent, "here and now,"
without any
possible postponement.  Life is fired at us point blank."
-- Ortega y Gasset

Graeme