Subject: Re: make update == make broken
To: Geert Hendrickx <firstname.lastname@example.org>
From: Sean Davis <email@example.com>
Date: 07/05/2005 07:33:12
On Tue, Jul 05, 2005 at 12:10:59PM +0200, Geert Hendrickx wrote:
> On Tue, Jul 05, 2005 at 05:43:38AM -0400, Sean Davis wrote:
> > show-needs-update is all well and good, but it doesn't do anything for
> > you if you just type 'make update' expecting it to update the one
> > package.
> Then your expectation is wrong. You should have read the documentation.
I have read the documentation. My expectation was for it to update mplayer,
and the stuff mplayer depends on. An update of mplayer has never caused an
update of KDE before; how hard would it be to simply print a prompt with a
timeout notifying the user that updating <x> is going to nuke <x,y,z,a,b,c>
also? We do it for PKG_OPTIONS.blah notifications, and those are
signifigantly less damaging to system functionality than removing half the
> > And the problem of backing up the packages if they're all going to be
> > deleted prior to building so that they can be reinstalled if they don't
> > build still needs to be addressed, for those of us who can't afford a
> > seperate build machine.
> pkgtools/pkg_comp makes a fine separate build machine, without extra costs.
Unless you consider the time required to build the release in addition to
the packages a cost.