Subject: Re: build.sh '-u' behavior problematic with new installs
To: Greg Troxel <firstname.lastname@example.org>
From: Frederick Bruckman <email@example.com>
Date: 09/25/2003 10:30:04
On Thu, 25 Sep 2003, Greg Troxel wrote:
> David Laight <firstname.lastname@example.org> writes:
> > 4) stale .depend files ?
> I'm pretty sure this is not the case - the build was from
> freshly-checked out source and an empty /usr/obj.
> The problem was that /usr/include/net/pfkeyv2.h was not installed, not
> that anything wasn't built.
> I had a similar problem with the contents of /usr/share/mk not getting
> updated on a machine that I took from 1.5 to 1.6 via source.
> Reflecting on all the comments, I favor changing the conditional
> install to install if timestamps differ or if content differs.
> But, it isn't clear that this is worth the effort.
Current's build.sh now supports installing to a destdir in one step,
then unconditionally installing the contents of the destdir to the
directory of your choice (e.g. "/") in the next. That's the solution
to the problem you encountered.