On Mon, 4 Apr 2005, Louis  Guillaume wrote:
> After fixing the issue with the first build (e.g. adding an 
> ACCEPTABLE_LICENCES entry) for that failure, I notice that certain packages 
> aren't just loaded from the binaries, they are rebuilt.
>
> Is this normal behaviour?

Depends on your DEPENDS_TARGET variable. You want bulk-install there, 
which should use existing binaries. No idea what you have in /etc/mk.conf.


> Also - I just noticed this, which is kind of contradictory to what I was 
> seeing before...
>
> In a certain .broken.html I see...
>
> BULK> Installing packages which are required to build 
> firefox-bin-flash-7.0.25.
> BULK>  /usr/sbin/pkg_add -K 
> /var/db/pkg/net/louis/packages/All/firefox-gtk2-bin-1.0.tgz
> pkg_add: Warning: package /net/louis/packages/All/firefox-gtk2-bin-1.0.tgz' 
> was built for a different version of the OS:
> pkg_add: NetBSD/i386 2.99.16 (pkg) vs. NetBSD/i386 3.99.3 (this host)
> pkg_add: Warning: package `/net/louis/packages/All/suse_gtk2-9.1nb3.tgz' was 
> built for a different version of the OS:
>
> ... etc.
>
> So some packages are being installed from binaries, somehow. I don't quite 
> get it.
>
> Under what conditions does a package get rebuilt?
> When do they get installed from an existing binary pacakge?

I think this is documented in the pkgsrc guide...


> I'm used to pkg_chk, but I wanted to give bulk builds a go. I'd like to build 
> the group of packages I "always" use in bulk, on a single machine, after each 
> new quarterly pkgsrc release.

I have no idea how that works. The bulk build framework was written to 
build all pkgs.


  - Hubert

-- 
NetBSD - Free AND Open!      (And of course secure, portable, yadda yadda)