Date: Fri, 23 May 2003 17:06:12 -0400 From: "Amit K. Rao" <arao@niksun.com> To: Craig Rodrigues <rodrigc@attbi.com>, freebsd-current@freebsd.org Subject: Re: Updating -CURRENT, what about outdated files? Message-ID: <200305231706.12519.arao@niksun.com> In-Reply-To: <20030523203517.GA93787@attbi.com> References: <20030523203517.GA93787@attbi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Something like this was covered a few times before. See for example: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=2154436+2157803+/usr/local/www/db/text/2003/freebsd-questions/20030323.freebsd-questions BTW, shouldn't "mergemaster -p" be before "make buildworld" ? On Friday 23 May 2003 04:35 pm, Craig Rodrigues wrote: > Hi, > > On one of my systems, I like to track -CURRENT, so I do a lot of: > - cvsup > - make buildworld > - make buildkernel > - make installkernel > - mergemaster -p > - make installworld > - mergemaster > > If I do this a lot, then sometimes my installed world may have > outdated libraries and header files. How can I make sure that > my installed tree doesn't have outdated stuff? > > For example, just before doing make installworld, I sometimes do: > rm -r /usr/include > > I am too scared to do this for /usr/lib or any other directory. > > Is there a good way to do what I want? > > Thanks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305231706.12519.arao>