On Mon, Jul 16, 2007 at 06:55:41PM -0400, Mark E. Perkins wrote:
> > Be aware that non-bootstrap builds don't set the precious flag any
> > longer.
> 
> What is the chicken/egg problem with pax?  It doesn't look to me as though
> installing pax needs pax (but I'm probably missing something obvious).  Making
> a binary package would need pax, I guess, but how does install need pax?

pkg_install uses pax in various places, e.g. pkg_add.

> What is the recommended way to update the tools installed at bootstrap?  Is a
> re-bootstrap the proper (and safe(st)) way to do this?

It is the best approach so far. It is one of the nasty and badly handled
cases left. That's why we avoid making incompat changes to pax. It will
drop out as dependency soon though.

Joerg