Date: Sun, 2 Jan 2005 20:33:23 -0500 (EST) From: Mikhail Teterin <mi@corbulon.video-collage.com> To: marcus@marcuscom.com (Joe Marcus Clarke) Cc: gnome@freebsd.org Subject: Re: mozilla vs. nspr Message-ID: <200501030133.j031XNei081006@corbulon.video-collage.com> In-Reply-To: <1104615240.38283.6.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sat, 2005-01-01 at 05:33 -0500, Mikhail Teterin wrote:
> > Why do www/mozilla and www/mozilla-devel build and install its own
> > versions of libnspr4 into ${PREFIX}/lib/mozilla(-devel)?
>
> Because they need to. The version of nspr that comes with Mozilla is
> newer than devel/nspr.
What's the need for the external nspr, then? Do some pieces of mozilla
build use the external and some -- the internal nspr? Can't they be
fixed?
> > The ports require and the resulting mozilla-bin executables use the
> > ${PREFIX}/lib/libnspr4.so...
>
> Yep, because if they tried to use the port version, they would get
> undefined symbol errors.
Sorry, I'm afraid, we misunderstand each other. Currently, the
installed mozilla uses the lib/libnspr4.so -- from devel/nspr, and not
lib/mozilla/libnspr4.so from www/mozilla. What's the need to even build
the different nspr inside www/mozilla? And if it is somehow needed
during build, what's the need to install it?
> > Can this be fixed -- to stop the "DLL hell"? Thanks!
>
> There's nothing broken. Both versions are unfortunate necessities.
I'm sorry, but using two different versions of the same software within
one application seems like a Bad Thing [TM]. Apps may do this, but the
good ports should not :-)
Yours,
-mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200501030133.j031XNei081006>