[Samba] RE: best way to work with cvs?

[Esh, Andrew]

I used to update my CVS sandbox this way. It was slow, and I had to wait.
Then I learned how to use rsync. Now I update my sandbox more often, and it
happens faster. I don't load down the CVS server either. If I want to be
certain I'm current, I can do a quick "cvs -qn update" to make sure rsync
got everything. It always does.

Here's what I run, to make a samba_22 sandbox and a samba_head sandbox in
/usr/local/src:

rsync -avz rsync://rsync.samba.org/ftp/unpacked/samba/
/usr/local/src/samba_head
rsync -avz rsync://rsync.samba.org/ftp/unpacked/samba_2_2/
/usr/local/src/samba_22

Of course this won't work if you aren't interested in getting the "latest"
samba.

-----Original Message-----
From: David Edward Shapiro [mailto:David.Edward.Shapiro at btitele.com]
Sent: Friday, March 01, 2002 7:31 AM
To: 'samba at lists.samba.org'
Cc: 'samba-technical at lists.samba.org'
Subject: best way to work with cvs?


I use a script to get the lastest samba:

#!/usr/bin/ksh
echo "\npassword: cvs\n"
cvs -d :pserver:cvs at pserver.samba.org:/cvsroot login
cvs -z5 -d :pserver:cvs at pserver.samba.org:/cvsroot co samba

Are there any other commands I could tack on or something I should do
differently to make sure I am getting correct rebuilds?

For example, should I tack on at the end:
cd /usr/local/samba/source
autoconf

or should I run some make commands?

I think I saw something about needing to run make proto some times?!?  

David

David E. Shapiro
Senior Unix Admin
BTi - the future of communications
4300 Six Forks Road, Raleigh, NC 27609
Office # 1-919-865-6955 
Pager # 1-800520-2354
Fax    # 1-919-863-7340



-------------- next part --------------
HTML attachment scrubbed and removed