From owner-freebsd-ports Wed Dec 1 12:34:20 1999 Delivered-To: freebsd-ports@freebsd.org Received: from viper.lovett.com (viper.lovett.com [216.60.121.173]) by hub.freebsd.org (Postfix) with ESMTP id E6A6515277 for ; Wed, 1 Dec 1999 12:34:09 -0800 (PST) (envelope-from ade@lovett.com) Received: from ade by viper.lovett.com with local (Exim 3.03 #1) id 11tGQm-000M3I-00; Wed, 01 Dec 1999 14:32:52 -0600 Date: Wed, 1 Dec 1999 14:32:52 -0600 From: Ade Lovett To: will andrews Cc: ports@FreeBSD.ORG Subject: Re: Problem on making kdevelop 1.0beta4.1 Message-ID: <19991201143252.L79505@lovett.com> References: <99112813355301.04840@mlobo.nlink.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from andrews@technologist.com on Tue, Nov 30, 1999 at 02:29:58PM -0500 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Nov 30, 1999 at 02:29:58PM -0500, will andrews wrote: > > [snip] > > 1) The kdelibs11 and qt142 ports are not set to use the newer g++ by > default. They need the USE_NEWGCC switch first. And there is nothing > I can do about these problems, since I am not the maintainer of > either of these ports. > > [snip] > > If you want any kind of kdevelop port committed to the ports tree for FreeBSD, > you will need to bug the following: > > 1) Maintainer of kdelibs11 port > 2) Maintainer of Qt 1.42 port Out of curiosity, has anyone contacted either Stefan or Andreas to get the necessary changes made? Alternatively (and this is addressed more to the committers that read -ports), if I or someone else come up with a set of patches to both qt142 and kde*11 that: (a) use USE_NEWGCC (b) bump the shared library version numbers so that it's obvious that (a) has happened. would they get committed -- ideally before a ports freeze for 3.4R -aDe -- Ade Lovett, Austin, TX. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message