From owner-freebsd-ports Sat Jan 8 9:37:32 2000 Delivered-To: freebsd-ports@freebsd.org Received: from asgaard.whispering.org (208-241-93-179.hsacorp.net [208.241.93.179]) by hub.freebsd.org (Postfix) with ESMTP id 32A5D150EA; Sat, 8 Jan 2000 09:37:26 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (23-125.008.popsite.net [209.69.197.125]) by asgaard.whispering.org (8.9.3/8.9.3) with ESMTP id MAA25043; Sat, 8 Jan 2000 12:37:13 -0500 (EST) (envelope-from will@blackdawn.com) Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id MAA12568; Sat, 8 Jan 2000 12:37:11 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000109013354I.imura@cs.titech.ac.jp> Date: Sat, 08 Jan 2000 12:37:11 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: "R. Imura" Subject: Re: Qt/KDE/bsd.port.mk upgrade PRs imminent Cc: andreas@FreeBSD.org, se@FreeBSD.org, asami@FreeBSD.org, ports@FreeBSD.org Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 08-Jan-00 R. Imura wrote: > You know, If replace, kde* port will be broken until they define USE_NEWGCC, > since they call same directory from their LIB_DEPENDs=. > What is your plan about it? Good point.. however, it seems to me that any port that depends on kde libraries will also depend on Qt, and thereby require USE_NEWGCC (through bsd.port.mk). Although.. they would have to be patched to require the newer KDE library (kdecore.3, kdeui.3, and so forth). Is there any reason why we don't have a "USE_KDE" switch in bsd.port.mk? Seems appropriate. Lots of ports would use it. Every time a version bump is made to the KDE 1.x libraries.. we'd have to modify all of them, too... ># I guess that why qt-1.x has stopped to 1.42 in the ports tree is related ># to some of gif problem. (See qt_gif.h in the Qt's source) ># And I also mention that latest qt-1.x is qt-1.45, though I have no plan ># to version up qt-i18n because of no serious problem. :) > ># I'm very sorry that I couldn't reply your kdevelop's PR, I've been sick.. :( No problem. I'm sending in a new one - this time, it'll depend on the recent Qt/KDE/bsd.port.mk submissions, plus it'll be an upgrade. No better place to start than with KDevelop 1.0. In fact, it was no problem at all to upgrade - I didn't have to change any patches. I just hope that Jeremy Lea's OPTIONAL_DEPENDS patch comes out sometime soon - or some people will be very unhappy with the lack of functionality. I know Qt has removed their GIF support - I should have mentioned this in the Qt14 port PR. I don't think any port will be affected by this, since Qt 1.44 can create PNG images anyway.. I didn't know there was a Qt 1.45.. Satoshi, I could send in another PR, and if you prefer, can make it "qt145" instead of "qt14".. simpler job. BTW, when you do a repo copy, does that involve copying the files and then patching, or does it involving importing and then copying CVS-related files? I need to know whether to provide a diff or a shar. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? P.S. Thanks for reminding me about the library dependencies.. I nearly forgot about them.. Satoshi, what do you say - we modify all current kde lib_depends, or add USE_KDE + modify all dependencies once? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message