Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Apr 2002 10:48:43 +1000
From:      Edwin Groothuis <edwin@mavetju.org>
To:        Kris Kennaway <kris@obsecurity.org>
Cc:        ports@FreeBSD.org, stable@FreeBSD.org
Subject:   Re: HEADS UP! XFree86 has been upgraded to 4.2.0 in 4.5-STABLE
Message-ID:  <20020428104843.K56612@k7.mavetju.org>
In-Reply-To: <20020427135344.D89190@xor.obsecurity.org>; from kris@obsecurity.org on Sat, Apr 27, 2002 at 01:53:44PM -0700
References:  <20020427044054.A78618@xor.obsecurity.org> <20020427221418.J56612@k7.mavetju.org> <20020427135344.D89190@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Apr 27, 2002 at 01:53:44PM -0700, Kris Kennaway wrote:
> On Sat, Apr 27, 2002 at 10:14:18PM +1000, Edwin Groothuis wrote:
> > On Sat, Apr 27, 2002 at 04:40:55AM -0700, Kris Kennaway wrote:
> > > As decided by the release engineering and port manager teams,
> > > I have switched the default XFree86 version from 3.3.6 to 4.2.0.
> > > Packages for FreeBSD 4.x are now being built with XFree86-4.2.0
> > > as a dependency, and ports will also be built with the newer
> > > version once you update to a newer -STABLE kernel.
> > 
> > XFree86-4.2.0 is currently depending on print/freetype2, which is
> > an often changing library (in the last six months we've gone from
> > libfreetype.so.6 to libfreetype.so.9). How will this problem be
> > attacked?
> 
> The same way it always is..when the shared library version is updated,
> the LIB_DEPENDS of any dependent ports will be updated to track it,
> and users who use an appropriate tool like portupgrade won't have
> any problems.

The problem what I was refering to was that an application from the
BASE OS was relying on a library in the PORTS SYSTEM.

Right now XFree86-4 is DYNAMICLY linked executable, which means
that if I replace a random-has-nothing-to-do-with-X PORT, suddenly
my BASE OS doesn't work anymore.

I wasn't talking about how port upgrades should be done, I know
that already thank you very much.


So, the question remains, how are they going to handle this problem?


Edwin

-- 
Edwin Groothuis      |           Personal website: http://www.MavEtJu.org
edwin@mavetju.org    |        Interested in MUDs? Visit Fatal Dimensions:
bash$ :(){ :|:&};:   |                    http://www.FatalDimensions.org/

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020428104843.K56612>