Date: Sun, 31 Dec 2006 22:12:50 -0300 From: Alejandro Pulver <alepulver@FreeBSD.org> To: pav@FreeBSD.org Cc: cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/Mk bsd.wx.mk Message-ID: <20061231221250.2ca7c1e0@phobos.mars.bsd> In-Reply-To: <20061231160946.71e9cd55@phobos.mars.bsd> References: <200612310434.kBV4YRXS037540@repoman.freebsd.org> <1167575429.1320.24.camel@ikaros.oook.cz> <20061231133753.4156b868@phobos.mars.bsd> <1167584645.1320.33.camel@ikaros.oook.cz> <20061231150344.25871955@phobos.mars.bsd> <1167590824.1320.52.camel@ikaros.oook.cz> <20061231160946.71e9cd55@phobos.mars.bsd>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_nl5l_4H3dq0bZzG3Hl=BSAz
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
On Sun, 31 Dec 2006 16:09:46 -0300
Alejandro Pulver <alepulver@FreeBSD.org> wrote:
> > > If I make the version to depend on the components, then when USE_PREMK
> > > is defined, the port won't be able to modify WX_COMPS after
> > > <bsd.port.pre.mk> (because the components can alter the version, and =
if
> > > then the port will think it's using one, but other will be used).
> >=20
> > Is this the problem with upcoming rollout of bsd.options.mk ?
> >=20
> > I mean, do you need to change WX_COMPS after bsd.port.pre.mk except when
> > handling OPTIONS and WITH_* flags?
> >=20
>=20
> No at least when the port checks variables defined after
> <bsd.port.pre.mk>, like ${ARCH}.
>=20
I have implemented this without losing flexibility.
Best Regards,
Ale
--Sig_nl5l_4H3dq0bZzG3Hl=BSAz
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)
iD8DBQFFmGAaiV05EpRcP2ERArl3AKCwPZwvvd7R8ZgeFQsn6hTdqNXevgCgtlaQ
hrnZbgiEIEQ3eG1YPXUifH8=
=+gZE
-----END PGP SIGNATURE-----
--Sig_nl5l_4H3dq0bZzG3Hl=BSAz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061231221250.2ca7c1e0>