Re: the make phases logic

[Marc Espie <espie@nerim.net>]

On Thu, Jul 01, 2004 at 08:46:11PM +0200, franciszek holop wrote:
> hello,
> 
> sometimes i just do a make fetch and/or make extract.
> lately i wanted to take a look at some files in the
> php sources so i did a make extract and it started to
> wildly download extensions and dependencies.
> 
> i was wondering why are the compile dependencies
> evaluated at this stage?  i just wanted to take a
> look at the code, and after all, extracting does
> not guarantee compiling, or does it?
> 
> i realize i can just download it and extract it,
> but why would i do that if we have this beautiful
> ports framework?  (Marc?)

Simpler for porters. We don't want N distinct series of dependencies.
Let's see, you have BUILD_DEPENDS, RUN_DEPENDS, LIB_DEPENDS and
REGRESS_DEPENDS already... pretty hard to reduce it some more.
By your scheme, you would need EXTRACT_DEPENDS or PATCH_DEPENDS.

To simplify stuff, all BUILD_DEPENDS/LIB_DEPENDS are evaluated before
extract. If you know what you're doing, set NO_DEPENDS=Yes like Nikolay
said.

In fact, all depends leave cookies behind for that reason, so that you
can do make extract NO_DEPENDS=Yes, and then make, and it will catch up.

But in case you try make extract NO_DEPENDS=Yes and it fails, then you
will know the BUILD_DEPENDS were needed for extract.