Subject: Re: pkg/17427
To: None <>
From: David Burgess <>
List: tech-pkg
Date: 07/19/2002 17:23:41
> Synopsis: Packages replace installed base components
> State-Changed-From-To: open->closed
> State-Changed-By: tron
> State-Changed-When: Fri Jul 19 06:58:30 PDT 2002
> State-Changed-Why:
> Packages should *hot* harm the base system in the way you suggest. Set
> your command search path to include "/usr/pkg/bin" and "/usr/pkg/bin"
> (for "root" only) and everything will work fine.

No it won't.  It will work exactly the way it does now.  I'll install a
new version of sendmail, and the makemap from the old system will be
executed.  I'll install a new version of named, and half of the old
programs will be used, and half of the new programs will be run.  Programs
that don't get the benefit of my local path changes don't work.  Cron jobs
don't work.
Did you think for a moment that I would miss something as simplistic as
setting the PATH?  Check your notes pal - I've been at this a little
longer than the five minutes you've just given me credit for.
If you can come up with a reason that required some thought on why being
able to update and upgrade system components based on the systems in
pkgsrc, I'd love to hear it.  Blowing me off is not going to make this
issue go away.
Dave Burgess
CTO, Nebraska On-Ramp
Chief Engineer, Mitec Internet Services
Bellevue, NE 68123