Date: Wed, 23 Feb 2000 12:43:33 -0800 (PST) From: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami) To: andrews@technologist.com Cc: andrews@technologist.com, ports@FreeBSD.org, imura@FreeBSD.org, se@FreeBSD.org Subject: Re: Qt/KDE upgrade path Message-ID: <200002232043.MAA23197@silvia.hip.berkeley.edu> In-Reply-To: <20000221020812.P44834@shadow.blackdawn.com> (message from Will Andrews on Mon, 21 Feb 2000 02:08:13 -0500) References: <20000220201511.L44834@shadow.blackdawn.com> <vqc66vj2gar.fsf@bubble.didi.com> <20000221020812.P44834@shadow.blackdawn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
(CC:d kde and kde-i18n maintainers -- yes, I know kde-i18n is already USE_NEWGCC'd, I just need your advice.) * From: Will Andrews <andrews@technologist.com> * > Don't worry about USE_NEWGCC. The next release is from 4-current, * > where USE_NEWGCC is a no-op anyway. We can fix that up after the * > release. * * Okay, so I guess it's all right to just optimize everything for -STABLE, * and fix them later. If that's the case I'll just push all my build * scripts over to the -current box and redo the patches. One thing though, adding NEW_GCC to be brought in with qt145 will cause the shlibs in -stable to be incompatible with previous versions. We need to bump the kde11* (non-i18n) shlib versions, and even though this only affects -stable, we probably need to do it now (before the release) to avoid -current's shlib versions being bumped right after the release. Which ones do we need to change? (Only C++ libs, right?) Stefan? (And in case Stefan is busy, Imura-san? :) 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?200002232043.MAA23197>