Subject: Re: make update
To: Jukka Marin <email@example.com>
From: David Brownlee <firstname.lastname@example.org>
Date: 05/17/2000 22:38:24
On Fri, 12 May 2000, Jukka Marin wrote:
> On Fri, May 12, 2000 at 01:53:54PM -0400, Andrew Gillham wrote:
> > Jukka Marin writes:
> > > BUT upgrading packages always drives me grazy. Yesterday, I wanted to install
> > > AbiWord.
> > Heh, I can't count the number of times I've rebuilt KDE because of this.
> I don't even want to _think_ how long this would take on my SS1+. This is
That is why we should have large sets of binary packages on
> the third day now and I still don't have AbiWord. Now I'm stuck because
> gnome-libs won't build - because it says "IMLIB 1.8 not installed - please
> install first" - although pkg_info says "imlib-1.9.8" has been installed.
People really _REALLY_ need to check dependencies when they update
a package. 'lintpkgsrc -d' will do a reasonable job. Maybe those
running bulk package builds would like to tag the output of
'lintpkgsrc -d' to the end?
> > I usually will end up run pkg_delete for *everything*, and starting over
> > from scratch.
> I guess that's the only way to get my machine going again. I think the
> package system was probably written by m$. "Got a problem? Easy! Just
> install everything again from scratch [thrice]!"
Its a difficult balance to achieve. In order to avoid ever hitting
the situation where a bunch of packages have been removed and
cannot be reinstalled you really need to build and install
everything into a different DESTDIR, _then_ pkg_delete and copy
across into PREFIX. You would probably want a first phase where it
created symlinks from DESTDIR to everything in PREFIX which was
needed for the packages being updated.
Anyone up for the job? :)
-- www.netbsd.org: No hype required --