Date: Tue, 6 Feb 1996 11:18:30 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: rkw@dataplex.net (Richard Wackerbarth) Cc: hackers@FreeBSD.org Subject: Re: On keeping a src tree Message-ID: <199602061818.LAA02651@phaeton.artisoft.com> In-Reply-To: <v02140b06ad3c9a165a9c@[199.183.109.242]> from "Richard Wackerbarth" at Feb 5, 96 11:51:20 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> FOLKS. This is EXCELLENT ADVISE. > > I suggest that you should never store the source code obtained from any > FreeBSD source in /usr/src. > > Move it somewhere else! I would go so far as to suggest that you make it > ReadOnly with respect to the account that you use to modify things. > > Then "clone" it into /usr/src using the lndir command. You can then use > this tree just as you would have originally. (Except that you have to copy > a source before you alter it) > > That way you will not polute the reference tree with your own stuff. How do you handle "config", since it is still (improperly, IMO) not built as part of the kernel build tree and wants to be installed? How do you generate diffs? For those of us without commit priviledges, we can't check into the main tree and have the code show up in our next SUP. I use "cvs diff" (I admit that this has only recently worked; I had to update my CVS to keep it from bombing out on my changed files on a "cvs update", and I had to disable the client and server code, since I did not want to install the new headers on my host system and code is still being built relative to the installed header files instead of the header files in the source tree, like you'd expect). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602061818.LAA02651>