Skip site navigation (1)Skip section navigation (2)
Date:      23 Feb 2000 17:21:35 -0800
From:      asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami)
To:        Will Andrews <andrews@TECHNOLOGIST.COM>
Cc:        ports@FreeBSD.ORG, imura@FreeBSD.ORG, se@FreeBSD.ORG
Subject:   Re: Qt/KDE upgrade path
Message-ID:  <vqcr9e39yzk.fsf@bubble.didi.com>
In-Reply-To: Will Andrews's message of "Wed, 23 Feb 2000 16:09:49 -0500"
References:  <20000220201511.L44834@shadow.blackdawn.com> <vqc66vj2gar.fsf@bubble.didi.com> <20000221020812.P44834@shadow.blackdawn.com> <200002232043.MAA23197@silvia.hip.berkeley.edu> <20000223160949.B33415@shadow.blackdawn.com>

next in thread | previous in thread | raw e-mail | index | archive | help
 * From: Will Andrews <andrews@TECHNOLOGIST.COM>

 * I already did the work to bump their shlib versions. You should read
 * about my work on my Qt/KDE site. :-)

Sorry.  I did take a look at it a while ago, but I thought you were
going to send-pr them.

 * Only the Qt and KDE libraries need shlib bumps.

Ok. Qt is already bumped (in qt145).  I looked at the others, there
appear to be many gratuitous changes (like reformatting CONFIGURE_ENV)
it's hard to tell where's the meat.  Other than bumping kdecore's
shlib version in LIB_DEPENDS, what is needed urgently (i.e., for
the upcoming 4.0R)?

 * The thing is, we'd need to patch many of the Qt/KDE-based ports to
 * ensure they work with USE_NEWGCC (temporarily breaking them on -stable)
 * before we upgrade the shlibs. Or else about 60 ports will be broken on
 * -stable. Well, I guess they'll get broken either way. :))

We can fix those after the release.  I don't want to ship 4.0R with
old Qt libs.

Satoshi


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




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