public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] qt3support USE flag. Is it needed now?
Date: Thu, 07 Oct 2010 17:14:55 -0500	[thread overview]
Message-ID: <4CAE465F.8090005@gmail.com> (raw)
In-Reply-To: <AANLkTim+qUaYux4YfpoNWfvOw_FM9LudDgj227cJxJEF@mail.gmail.com>

Paul Hartman wrote:
> On Thu, Oct 7, 2010 at 2:40 PM, Dale<rdalek1967@gmail.com>  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?

Dale

:-)  :-)



  reply	other threads:[~2010-10-07 22:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 19:40 [gentoo-user] qt3support USE flag. Is it needed now? Dale
2010-10-07 19:51 ` Alan McKinnon
2010-10-07 20:03   ` [gentoo-user] " Nikos Chantziaras
2010-10-07 20:17     ` Alan McKinnon
2010-10-07 19:54 ` [gentoo-user] " Alan McKinnon
2010-10-07 20:03 ` [gentoo-user] " Nikos Chantziaras
2010-10-07 20:03 ` [gentoo-user] " Paul Hartman
2010-10-07 22:14   ` Dale [this message]
2010-10-07 22:47     ` [gentoo-user] " Nikos Chantziaras
2010-10-07 23:17       ` Dale
2010-10-07 23:24         ` Nikos Chantziaras
2010-10-07 23:31           ` Dale
2010-10-07 23:52             ` Alan McKinnon
2010-10-08  8:50     ` [gentoo-user] " Neil Bothwick
2010-10-08 14:53       ` Dale
2010-10-07 22:10 ` Peter Humphrey
2010-10-07 22:24   ` Dale
2010-10-07 22:49     ` [gentoo-user] " Nikos Chantziaras
2010-10-07 23:15       ` Dale
2010-10-08  9:47       ` Arttu V.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CAE465F.8090005@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox