From owner-freebsd-ports Mon Jan 10 8:38:14 2000 Delivered-To: freebsd-ports@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id 6A02514DEF; Mon, 10 Jan 2000 08:38:12 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca44-58.ix.netcom.com [209.111.212.186]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id IAA58253; Mon, 10 Jan 2000 08:38:05 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id IAA79755; Mon, 10 Jan 2000 08:38:01 -0800 (PST) To: Will Andrews Cc: "R. Imura" , andreas@FreeBSD.org, se@FreeBSD.org, ports@FreeBSD.org Subject: Re: Qt/KDE/bsd.port.mk upgrade PRs imminent References: From: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami) Date: 10 Jan 2000 08:37:58 -0800 In-Reply-To: Will Andrews's message of "Sat, 08 Jan 2000 12:37:11 -0500 (EST)" Message-ID: Lines: 27 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: Will Andrews * 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). Yes, this should all be committed at once. * 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... Because the version doesn't bump that often? :) Also, different ports may require different parts (or languages) of kde. Or do you think it's ok to just always use kdelibs? * 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. Copying and then patching, so unless the new port looks nothing like the old one, a diff would be better. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message