Date: Tue, 08 Oct 2002 00:38:51 -0600 From: Lyndon Nerenberg <lyndon@orthanc.ab.ca> To: "M. Warner Losh" <imp@bsdimp.com> Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: Do we still need portmap(8)? Message-ID: <200210080638.g986cpGI085484@orthanc.ab.ca> In-Reply-To: Your message of "Mon, 07 Oct 2002 11:20:56 MDT." <20021007.112056.119814448.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "M" == M Warner Losh <imp@bsdimp.com> writes:
M> I think that we need a mtree.obsolete that goes through and
M> deletes these sorts of things as part of installworld/upgrade
M> scripts.
No solution like this will ever work for everyone, or in every
situation. For example, you generally want to nuke stale bits from
/usr/include, but doing the same in /usr/lib can lead to Interesting
Times. And you never know if I might be working on replacements for
obsoleted bits of the OS that I'm installing into their old
location. For example: adduser. Current would remove it in your
scenario, even though I've re-implemented it in it's old location in my
build/install tree. Yes, I could modify mtree.obsolete under /usr/src,
but that seems counter-productive for a -current
environment. (Thankfully, I don't own a bike, so I don't need to worry
about the colour of it's shed.)
One compromise is to have the 'install' target touch a timestamp file
before setting off to overwrite things. Then you can use 'find <mumble>
! -newer ...' to search for and display possibly stale files. (A
/usr/sbin/findstale script that wraps this might be a useful adjunct to
mergemaster.) I use /bin/cat as a timestamp file for rough analysis
purposes.
--lyndon
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210080638.g986cpGI085484>