Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 31 Dec 1998 06:14:35 -0600
From:      "Matthew D. Fuller" <fullermd@futuresouth.com>
To:        Sheldon Hearn <axl@iafrica.com>
Cc:        "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, freebsd-stable@FreeBSD.ORG
Subject:   Re: Sendmail Anti-SPAM stuff
Message-ID:  <19981231061435.B10659@futuresouth.com>
In-Reply-To: <21034.915102433@axl.noc.iafrica.com>; from Sheldon Hearn on Thu, Dec 31, 1998 at 01:07:13PM %2B0200
References:  <19981230235645.A10659@futuresouth.com> <21034.915102433@axl.noc.iafrica.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 31, 1998 at 01:07:13PM +0200, Sheldon Hearn woke me up to tell me:
> 
> It turned out to be a huge waste of time because my guru pointed out
> something very elegant called CVS, which I've been sold on ever since
> and makes any such solution _completely_ unnecessary.

I use CVSup to maintain a local copy of the FreeBSD CVS repository, and
use CVS to handle my source/ports/etc.  I also use CVS for several of my
own projects.
But in this case, CVS is slightly less than perfect.  For one thing, we
have several different machines with different configs here.  It's not
uncommon at all that I wipe /usr/src clean (/usr/src and /usr/obj have
their own partitions, thank god), so for any of this to be of any
practical use, I'd need to import my own changes onto a seperate branch,
which lends itself to some fairly severe ugliness there.  I supposed I
could create a seperate 'local' module, and check it out OVER the src
module, and try to keep it up with any/all changes, etc.  Or I could
branch at some arbitrary point back in the tree in the files I'm
interested in with a LOCAL symbolic tag on the branch, but I'm not sure
what CVSup would do to that; whether it would wipe my local changes when
there's a change to the master RCS file in question, or keep them, or
create some god-awful mess by mixing the two.  I'm not horribly fond of
either solution.
I'd think there should be some way to generalize that nicely in a
make.conf knob; that also makes it so it's automatic that each machine is
configured right for any/all local changes on it (I NFS mount /usr/src
and /usr/obj from my build machine to each machine, and do a make
installworld; takes about 15 minutes, not too shabby), since each machine
would reference it's local /etc/make.conf, and 'exclude' X, Y, and Z from
the install process.

Food for thought...


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
|       FreeBSD; the way computers were meant to be       |
* "The only reason I'm burning my candle at both ends, is *
| that I haven't figured out how to light the middle yet."|
*    fullermd@futuresouth.com      :-}  MAtthew Fuller    *
|      http://keystone.westminster.edu/~fullermd          |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981231061435.B10659>