From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1P3zvz-0000Yr-Ag for garchives@archives.gentoo.org; Thu, 07 Oct 2010 23:31:36 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id ED7AFE09B7; Thu, 7 Oct 2010 23:31:05 +0000 (UTC) Received: from mail-yx0-f181.google.com (mail-yx0-f181.google.com [209.85.213.181]) by pigeon.gentoo.org (Postfix) with ESMTP id CBA9DE09B7 for ; Thu, 7 Oct 2010 23:31:05 +0000 (UTC) Received: by yxh35 with SMTP id 35so262132yxh.40 for ; Thu, 07 Oct 2010 16:31:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=hPtBj9g3vnh0Kr+iDw0+rmpPPhMoVZ/mMvrBuVzN7Ag=; b=TD2FrnQvk5DjpjpCFe+85qmcJJGSyTo2fqjbRiNyFrwogEEH9azG9T2bNSXcrgpDR5 vBKNQaFxpBUW9W0/dlIQUKI4ZZ7+JJhzrt8HPIjhXUhlPaYvvG+JTsKDFhPcLJ1at7c/ 8Jk6exuTk2f0KyNFiHmk1f2EVHAJJ9zVo8a/E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=djslcsIBChw4XkzeOvYyXeWBkBctyCdNnNYQgigd3oTA0P2rSw3GUNPp9eETMhmqy7 ActmR871H/vKZ8bQDg9Hd+ig4GV7U2tcR/uDa9FF8BHNpwj27Nwv+0cj1LdZhKJCqAme o1mWr5iFPLHH3eV7wM+o0oGOpkfPVh0MH4hpQ= Received: by 10.236.108.35 with SMTP id p23mr3281674yhg.56.1286494265550; Thu, 07 Oct 2010 16:31:05 -0700 (PDT) Received: from [192.168.1.2] (adsl-0-122-233.jan.bellsouth.net [65.0.122.233]) by mx.google.com with ESMTPS id n48sm1735284yha.7.2010.10.07.16.31.03 (version=SSLv3 cipher=RC4-MD5); Thu, 07 Oct 2010 16:31:04 -0700 (PDT) Message-ID: <4CAE5836.7080907@gmail.com> Date: Thu, 07 Oct 2010 18:31:02 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.13) Gecko/20101006 Gentoo/2.0.8-r1 SeaMonkey/2.0.8 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: qt3support USE flag. Is it needed now? References: <4CAE2230.8020603@gmail.com> <4CAE465F.8090005@gmail.com> <4CAE5508.2050503@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 5d14405f-90f4-41d7-ab8f-b15106990ef0 X-Archives-Hash: 4c8cc316da6bfe7bfe53c1cbad1661e6 Nikos Chantziaras wrote: > On 10/08/2010 02:17 AM, Dale wrote: >> Nikos Chantziaras wrote: >>> On 10/08/2010 01:14 AM, Dale wrote: >>>> Paul Hartman wrote: >>>>> On Thu, Oct 7, 2010 at 2:40 PM, Dale wrote: >>>>>> Hi, >>>>>> >>>>>> I have a question. I'm using KDE4, about to switch to 4.5.2. Do I >>>>>> need >>>>>> qt3support anymore? I'm talking about the USE flag qt3support. I run >>>>>> into >>>>>> blocks sometimes and I know KDE3 needed qt3. I'm just curious if I >>>>>> can get >>>>>> rid of this USE flag now. I only have KDE4 installed. No more KDE3 >>>>>> left >>>>>> that I know of. >>>>> Going along with what Alan said. qt3support does not use Qt 3 at all. >>>>> It just puts something like a Qt 3-compatible API into Qt 4, to make >>>>> porting Qt 3 to Qt 4 apps easier. It is largely insignifcant to you >>>>> (since it's not pulling in qt3 packages). >>>>> >>>>> If you have any packages that require this USE flag, their ebuild >>>>> will >>>>> require this USE flag. So disable it, emerge --deep --newuse world >>>>> and >>>>> see if it complains. If it does, re-enable and continue life with >>>>> qt3support as if nothing ever happened. :) >>>>> >>>> >>>> Just picking the last message to reply to so this is for everyone who >>>> has chimed in so far. >>>> >>>> I may remove the USE flag and just see what blows up. I may copy over >>>> some binaries so that I can just use -k and not have to wait on the >>>> compiles. I would think if I remove it that something would pitch all >>>> holy hell about it if it has to have it. I'm sure it would be >>>> caught at >>>> some point and I would know it then for sure. >>>> >>>> I'm not sure if I have anything on here that must have qt3support. Is >>>> there a way to know for sure? Maybe some obscure command that I am not >>>> familiar with? >>> >>> revdep-rebuild will help. The qt3support USE flag is nothing magical; >>> it simply pulls the "x11-libs/qt-qt3support" as a dependency. This >>> package installs the /usr/lib/qt4/libQt3Support.so.* libraries. So if >>> you have binaries that try to load this lib, revdep-rebuild will find >>> them. >>> >>> And in general, if *any* binary you try to run aborts with something >>> like "libQt3Support.so not found" or similar, then you know it needs >>> qt3support. >>> >>> >> >> I didn't want to remove it and recompile just to find out KDE won't work >> anymore. That would be . . . bad. lol > > There's the "rm" command, and then there's "mv". > But I would still have to recompile again with the qt3support flag if it messed up badly. On this machine, that takes time. During that time, I may not have KDE at all. I did that when I made a mistake a while back. About 12 hours with no GUI. That was with some packages being binary and using -k. If I have to recompile them all, it would take longer still. Not something I want to repeat. Dale :-) :-)