Re: /usr/src/Makefile.inc1: make update

2000-02-08 Thread John Polstra
In article <[EMAIL PROTECTED]>, Patrick M. Hausen <[EMAIL PROTECTED]> wrote: > > Yes, but now we have three different ways to update: [...] > 2. call cvsup from /usr/local/etc/periodic with supfiles for whatever you >need ... Not a good idea. Add a new crontab entry instead. If everybody u

Re: /usr/src/Makefile.inc1: make update

2000-02-07 Thread Christian Weisgerber
Bill Fumerola <[EMAIL PROTECTED]> wrote: > As the person who implemented PORTSSUPFILE, I'd object. Originally > SUPFILE2 was set to the ports-supfile, so to preserve original > behavior (that is, updating ports along with src/) that stayed in. Very well. > To some of us, updating both at the sa

Re: /usr/src/Makefile.inc1: make update

2000-02-07 Thread Patrick M. Hausen
Hi all! Bill Fumerola wrote: > On Mon, Feb 07, 2000 at 10:31:17PM +0100, Christian Weisgerber wrote: > > > Why does "make update" in /usr/src also include a cvsup of /usr/ports? > > > > Since /usr/ports and /usr/docs have Makefiles and "update" targets > > of their own, and the alternative upd

Re: /usr/src/Makefile.inc1: make update

2000-02-07 Thread Bill Fumerola
On Mon, Feb 07, 2000 at 10:31:17PM +0100, Christian Weisgerber wrote: > Why does "make update" in /usr/src also include a cvsup of /usr/ports? > > Since /usr/ports and /usr/docs have Makefiles and "update" targets > of their own, and the alternative update by cvs doesn't cover > /usr/ports eithe