Subject: Re: how to update a pkg marked not for deletion?
To: None <>
From: Mark E. Perkins <>
List: pkgsrc-users
Date: 07/16/2007 18:55:41
On 2007/07/16 06:03, Joerg Sonnenberger wrote:
> On Sun, Jul 15, 2007 at 03:13:34PM -0400, Mark E. Perkins wrote:
>> Having updated pkg_install, I thought I might as well update the other
>> pkgtools that changed recently (pax, tnftp).  But they're marked as not for
>> deletion, so they cannot be deleted. :-)  None of the suggestions in the error
>> messages (pkg_delete, make {update,replace}) works.  So how *does* one go
>> about updating them?
> I don't think we offer a normal way to update pax (chicken and egg
> problem). tnftp can be just removed with pkg_delete -ff and reinstalled.
> 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?

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?

This should be documented in the Guide.  I don't see anything in the Guide
about keeping the basic tools up to date.