Hi,

I've been wondering about 'make update' as well.  It's not clear to me, but 
it seems to be you would use this command to update most if not all of the 
packages you have installed.  In other words, I had KDE 3.4.0 installed, and 
I'm now running 'make update' from /usr/pkgsrc/meta-pkgs/kde3/ and it's 
building dependency packages and who knows what all else.  I don't know if 
it's broken (I hope not), but I do agree with you that the order and the way 
in which it works should be looked at.

-Robert

----- Original Message ----- 
From: "Sean Davis" <dive-nb@endersgame.net>
To: <tech-pkg@netbsd.org>
Sent: Thursday, June 23, 2005 12:08 PM
Subject: make update


> As the mail sent yesterday seems to have disappeared into the ether, I'll 
> try
> again.
>
> make update is terribly broken. It is not correct, nor can I see how it 
> was
> ever thought to be correct, to wipe out every package with a pkg_delete -r
> before it's even known if they'll build (commonly leaving one with half 
> the
> packages they had, if they do it on something like mplayer, have KDE
> installed, and KDE doesn't build...)
>
> Why does it work like this? Is there any plan to fix it so that it builds
> the packages first, and if they build, then nuke the old versions and
> install the new? pkg_comp isn't really a solution... having to build an
> entire release of NetBSD to build one package is pretty silly, and there 
> are
> packages that won't build under pkg_comp, such as kdeaddons. (at least, it
> wouldn't the last time I tried it. I haven't had time to setup a pkg_comp
> chroot in a while.)
>
> Any suggestions? Is anybody working on this?
>
> -Sean
>