portupgrade failure

[Matthew Seaman]

Miroslav Lachman wrote:
> Adam McDougall wrote:
> [...]
>> Some of that sounds true to my experience, for a while I've noticed while
>> installing a new port with portupgrade that it will install the default
>> dependencies before prompting with the options screen to find out which
>> ones I want.  For example if I do 'portupgrade -N postfix' on a fresh
>> system, it will first install pcre and THEN prompt me to (de)select pcre
>> or any of the other optional deps.
> [...]
> 
> It was tired by this behavior more than year ago and it was the main 
> reason to me to switch to portmaster. I got system bloated with unwanted 
> dependencies when using portinstall/portupgrade. I never found what 
> causes this in portupgrade.

It's actually exactly what would happen if you did:

   # cd /usr/ports/mail/postfix
   # make install

ie. The OPTIONS settings are only processed after the BUILD_DEPENDS
dependencies have been fulfilled.  This is mostly because OPTIONS processing
always used to happen through the inclusion of bsd.port.pre.mk
 
As of a few months ago, there is now a bsd.port.options.mk standard Makefile
that can be included earlier in the port's Makefile and that has an effect
much earlier in the build process, but it depends on port maintainers
updating their ports to take account of this.  (So far, I've only updated
one of my ports -- textproc/sphinxsearch -- but I was planning to deal with
the rest Real Soon Now.)

	Cheers,

	Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
                                                  Kent, CT11 9PW

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20091217/45f78faa/signature.pgp