Subject: Re: depend on nspr instead of ${MOZILLA}? (was Re: Debugging a buildlink wrapper problem?)
To: walt <>
From: Geert Hendrickx <>
List: tech-pkg
Date: 08/09/2005 14:27:02
On Tue, Aug 09, 2005 at 05:08:39AM -0700, walt wrote:
> On Tue, 2005-08-09 at 11:52 +0200, Geert Hendrickx 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 file, I think we could
> > > best make it an option on which to depend.  
> > 
> > I've figured out an 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 package:
> > devel/nspr.  Should I use this one, to keep things easy?  Then the option
> > is just whether or not to build the plugin.  
> I believe we need only the nspr header files, is this right?  Could
> we just include those headers as a patch file as part of the jdk14
> package?

Hm, that would be duplication, I prefer to use the nspr package.  It's only
a build-time dependency, you can get rid of it later.  (and some people may
have it on their system already since it's (indirectly) required by gaim.)