Subject: Re: avoiding unnecessary recompilation ...
To: Todd Vierling <firstname.lastname@example.org>
From: Malcolm Herbert <email@example.com>
Date: 01/16/2006 10:42:45
On Sun, Jan 15, 2006 at 08:45:20AM -0500, Todd Vierling wrote:
|On Sun, 15 Jan 2006, Malcolm Herbert wrote:
|> Speaking of perl, it seems that perl and things that depend on it
|> are recompiled in the bulk build area even if there are no revision
|> changes and a compiled package of the same revision is available ...
|> is there any way to prevent this?
|"make replace", for one. It didn't work on perl5 in the days before the
|binary compatibility overhaul, but it now does.
ah, I am wanting to keep using the bulk build environment to do package
builds from within that so that I force myself to keep a record of the
packages I want in /etc/mk.conf - so that when I do want to rebuild the
lot it all Just Works ...
The problem is that if I build a package in an ad-hoc manner using make
package in the same chroot environment (it's the only package build
environment I have) things don't seem to be smart enough to do the bulk
build trick of installing package dependancies from binary packages if
they're available and so it remakes them ...
Worse, this causes the bulk build to rebuild them all again because the
timestamps get out of sync ...
|As far as bulk builds go, there is the switch USE_BULK_TIMESTAMPS=no,
|which turns off recompiling for only file timestamp changes (binpkg or
|package-dir file times).
Ah, that's probably what I want - thanks ...
|Be aware that you need to have more trust in pkgsrc's commitment to
|binary compatibility wrt buildlink3 if you use this setting.
Fair enough - I plan on running a normal bulk build after a CVS update,
which should sort out that problem ...
Malcolm Herbert This brain intentionally
firstname.lastname@example.org left blank