From owner-freebsd-ports@FreeBSD.ORG  Mon May 16 21:31:48 2011
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id DE65A106566B;
	Mon, 16 May 2011 21:31:48 +0000 (UTC)
	(envelope-from shaun@FreeBSD.org)
Received: from alpha.inerd.com (alpha.inerd.com [204.109.56.118])
	by mx1.freebsd.org (Postfix) with ESMTP id AF0598FC0A;
	Mon, 16 May 2011 21:31:48 +0000 (UTC)
Received: from charon.picobyte.net (localhost [127.0.0.1])
	by alpha.inerd.com (Postfix) with ESMTP id C50B9147CD7;
	Mon, 16 May 2011 21:14:14 +0000 (UTC)
Date: Mon, 16 May 2011 22:14:14 +0100
From: Shaun Amott <shaun@FreeBSD.org>
To: Doug Barton <dougb@FreeBSD.org>
Message-ID: <20110516211413.GA51480@charon.picobyte.net>
References: <4DD09B45.9070306@FreeBSD.org>
	<alpine.BSF.2.00.1105152216460.20421@wonkity.com>
	<BANLkTin08WiMbkzpKmq_zaz2cGp0esMJxg@mail.gmail.com>
	<alpine.BSF.2.00.1105160754150.22315@wonkity.com>
	<BANLkTi=ZV75sVcW_wf9mvjad2EV6TVrZmg@mail.gmail.com>
	<4DD17E78.20003@FreeBSD.org>
	<BANLkTimqJVnb8BnJKaDNWBZw=OvZpk1hnw@mail.gmail.com>
	<4DD189D2.3060106@FreeBSD.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK"
Content-Disposition: inline
In-Reply-To: <4DD189D2.3060106@FreeBSD.org>
User-Agent: Mutt/1.5.20 (FreeBSD i386)
Cc: Warren Block <wblock@wonkity.com>, ohauer@freebsd.org,
	FreeBSD Ports <freebsd-ports@freebsd.org>, utisoft@gmail.com
Subject: Re: proper use of bsd.port.options.mk
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2011 21:31:49 -0000


--YZ5djTAD1cGYuMQK
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, May 16, 2011 at 01:32:18PM -0700, Doug Barton wrote:
> On 05/16/2011 13:17, Chris Rees wrote:
> > You can't define USE_JAVA_after_  bsd.port.pre.mk and expect JAVA_PORT
> > to be defined...
>=20
> What I'm looking for is an actual example of something that doesn't work=
=20
> for the common case. Where "actual" includes a path to a port that I can=
=20
> test.
>=20
> And I'm not trying to be a pita here, I have two goals; one is to update=
=20
> my ports to use bsd.port.options.mk, and the other is to get the=20
> documentation updated. I don't want to do either until we are all sure=20
> that we know the facts accurately.
>=20

The documentation in bsd.port.options.mk is correct (although perhaps
not entirely clear).

net-mgmt/ettercap contains an example of the problem this file was
supposed to address: the port has to manually include bsd.openssl.mk in
order to access $OPENSSLBASE, rather than using the canonical
$USE_OPENSSL variable.

--=20
Shaun Amott // PGP: 0x6B387A9A
"A foolish consistency is the hobgoblin
of little minds." - Ralph Waldo Emerson

--YZ5djTAD1cGYuMQK
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEARECAAYFAk3Rk6UACgkQkmhdCGs4epq7TgCfSjpHmK+IFJCKddCkAoqg3rWi
QOQAoOzcx/V/6lfFc+HuPwFtCJNrOeYf
=4KFd
-----END PGP SIGNATURE-----

--YZ5djTAD1cGYuMQK--