Subject: Re: "make update" thought...
To: Hubert Feyrer <email@example.com>
From: Rene Hexel <firstname.lastname@example.org>
Date: 09/16/1999 07:40:21
Hubert Feyrer wrote:
> What about any required packges (dependencies)?
> You'll have to install them to build the new package, and for
> that you'll have to remove the old dependencies first. Doesn't
> seem to buy much, sorry.
Hmm, IMHO there are several TODO's for the update target:
* better support for resuming an interrupted 'make update'. At
least, we should prevent the user from calling 'make update'
w/o REINSTALL=1 a second time (this should only work after a
'make clean'), and issue an apropriate warning.
* A downstream 'clean-update' (or whatever) target that works
like 'clean-depends', but in the other direction.
* A way of automatically updating dependencies (upstream) as
well. This might open a can of worms, and I'm not quite
sure yet how to do this. For starters, we could make that
optional, e.g., through a UPDATE_DEPENDS=1 switch.
* A way of fetching files first, before running 'pkg_delete'.
This could either be done automatically (through a two-pass
mechanism) or through an 'update-fetch-list' target.