Re: pbulk with manual steps

[Joerg Sonnenberger <joerg%britannica.bec.de@localhost>]

On Sun, Jan 03, 2016 at 09:15:48AM +0100, Havard Eidnes wrote:
> And ... as demonstrated, it's no longer a good idea to use the
> pkg_install installed in /usr/pbulk/sbin as the "pbulk pkg_install",
> such as directed by the pbulk.conf example config file, because those
> programs default to operating on the binaries in /usr/pbulk and the
> pkg db in /usr/pbulk/var/db/pkg, and pbulk apparently doesn't
> (anymore?) explicitly specify -K and -p options to direct them to
> operate on /usr/pkg and /var/db/pkg instead.

They explicitly pass the database. They do not override the prefix as
the prefix is reocrded in the package. I still have not seen whatever
pbulk.conf you are using, so I can only guess about your problems.

> >> I see that when mk/pbulk/pbulk.sh is invoked with no arguments, it
> >> will create a bootstrap kit, and append a setting of bootstrapkit=
> >> to pbulk.conf.  Whether that's actually used is for me as an
> >> operator difficult to tell from the log file produced by bulkbuild.
> > 
> > It is used if it is referenced by pbulk.conf. I don't remember right now
> > that version of pkg_install is in netbsd-6 to know if a bootstrap kit is
> > the best option even on NetBSD for that branch. It is currently not
> > needed or useful for netbsd-7 and -current.
> 
> My point is that if the distinction between "are you using a bootstrap
> kit" and "are you *not* using a bootstrap kit" is significant to guide
> the operator, its usage ought to be prominently noted in the log file.
> It currently isn't.

It is nowhere as important as you try to make it sound. If you need to
bootstrap, it is pretty evident by the dependency tree and the expected
build errors.

Joerg