Re: -R for make update ?

2001-05-22 Thread Terry Lambert
Wilko Bulte wrote: Hi Is there any specific reason why one needs to be able to write a lock to the CVS repo when running 'make update' to get a freshly checked out source? Yeah: you aren't running your CVS server in pserver mode, and so are trying to do a lock, either in your local copy,

Re: -R for make update ?

2001-05-22 Thread Kris Kennaway
On Tue, May 22, 2001 at 04:00:31AM -0700, Terry Lambert wrote: Is there any specific reason why one needs to be able to write a lock to the CVS repo when running 'make update' to get a freshly checked out source? Yeah: you aren't running your CVS server in pserver mode, and so are

Re: -R for make update ?

2001-05-22 Thread Nate Williams
Is there any specific reason why one needs to be able to write a lock to the CVS repo when running 'make update' to get a freshly checked out source? Yeah: you aren't running your CVS server in pserver mode, and so are trying to do a lock, either in your local copy, or over NFS.

Re: -R for make update ?

2001-05-22 Thread Kris Kennaway
On Tue, May 22, 2001 at 02:15:18PM -0600, Nate Williams wrote: Is there any specific reason why one needs to be able to write a lock to the CVS repo when running 'make update' to get a freshly checked out source? Yeah: you aren't running your CVS server in pserver mode, and

-R for make update ?

2001-05-21 Thread Wilko Bulte
Hi Is there any specific reason why one needs to be able to write a lock to the CVS repo when running 'make update' to get a freshly checked out source? The Makefile.inc1 has: .if defined(CVS_UPDATE) @echo --

Re: -R for make update ?

2001-05-21 Thread Josef Karthauser
On Mon, May 21, 2001 at 07:48:28PM +0200, Wilko Bulte wrote: Hi Is there any specific reason why one needs to be able to write a lock to the CVS repo when running 'make update' to get a freshly checked out source? The Makefile.inc1 has: .if defined(CVS_UPDATE) @echo

Re: -R for make update ?

2001-05-21 Thread Dan Nelson
In the last episode (May 21), Wilko Bulte said: Is there any specific reason why one needs to be able to write a lock to the CVS repo when running 'make update' to get a freshly checked out source? The Makefile.inc1 has: .if defined(CVS_UPDATE) cd ${.CURDIR}; cvs -q update -A -P -d