Subject: Re: depend on nspr instead of ${MOZILLA}? (was Re: Debugging a buildlink wrapper problem?)
To: ghen@telenet.be, Geert Hendrickx <geert.hendrickx@ua.ac.be>
From: Julio M. Merino Vidal <jmmv84@gmail.com>
List: tech-pkg
Date: 08/09/2005 14:04:16
On 8/9/05, Geert Hendrickx <geert.hendrickx@ua.ac.be> wrote:
> On Sun, Aug 07, 2005 at 10:59:51PM +0200, Geert Hendrickx wrote:
> > Good news!  Now we must make it work with any of the Mozilla/Firefox
> > packages.  As they each have their own buildink3.mk file, I think we co=
uld
> > best make it an option on which to depend.
>=20
> I've figured out an options.mk file so the user can choose which mozilla =
to
> use as a build-dependency for the (optional) jdk14-plugin.  But I just
> found out that all the include files needed are also in a separate packag=
e:
> devel/nspr.  Should I use this one, to keep things easy?  Then the option
> is just whether or not to build the plugin.

Please use nspr if possible (ideally, our mozilla packages could use that t=
oo,
instead of rebuilding it from their own sources).

And... to avoid the build-time option, could you split the plugin in its ow=
n
independent package?

Cheers,

--=20
Julio M. Merino Vidal <jmmv84@gmail.com>
http://www.livejournal.com/users/jmmv/
The NetBSD Project - http://www.NetBSD.org/