Date: Sun, 30 Aug 2009 10:07:24 -0700 (PDT) From: Doug Barton <dougb@FreeBSD.org> To: Miroslav Lachman <000.fbsd@quip.cz> Cc: ale@freebsd.org, freebsd-ports@freebsd.org Subject: Re: portmaster is not always recursive Message-ID: <alpine.BSF.2.00.0908300952370.43298@qbhto.arg> In-Reply-To: <4A999B4A.3000603@quip.cz> References: <4A89CB20.3000408@quip.cz> <4A8E2121.6040507@FreeBSD.org> <4A8E8ACA.3060705@quip.cz> <4A8EF583.8090806@FreeBSD.org> <4A9966FE.7060509@quip.cz> <4A998242.80005@FreeBSD.org> <4A999B4A.3000603@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Ok, I found the problem, but the bad news is that I don't know what the
solution is going to be. I've cc'ed ale since what I'm seeing is weird
behavior by the php5-mcrypt slave port.
What portmaster does by default when looking for dependencies is to run
'make build-depends-list run-depends-list | sort -u' to get the list of
things to check. I used to just do all-depends-list by default but users
complained that it was creating problems by recursing so far down the
tree.
What I'm seeing in security/php5-mcrypt is that the union of
{build|run}-depends-list is different if I run it in the slave port than
if I run it in lang/php5 (after enabling the OPTION for apache):
In the slave port:
/usr/ports/devel/autoconf262
/usr/ports/devel/libltdl22
/usr/ports/lang/php5
/usr/ports/security/libmcrypt
In lang/php5:
/usr/ports/devel/autoconf262
/usr/ports/devel/pkg-config
/usr/ports/textproc/libxml2
/usr/ports/www/apache22
That's why portmaster is not picking up the dependency on apache when
updating php5-mcrypt.
Miroslav, for your specific problem you can add the -t option to
portmaster to force it to do all-depends-list, which will cause portmaster
to "see" the apache dependency. Other than that I'm not sure how to
proceed. I suppose that I could force all-depends-list if MASTERDIR is set
in a Makefile, but I'm kind of hesitant to do that unless it becomes
obvious that the problem is more widespread.
hope this helps,
Doug
- --
This .signature sanitized for your protection
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (FreeBSD)
iEYEAREDAAYFAkqasc8ACgkQyIakK9Wy8PuHsACbBFlBJWJL0hj8L1MtOc78fEq6
dN4AoKz4eCJRpquOh5BoYxr5Z3Dov+3c
=1/H3
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0908300952370.43298>