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] Re: qt3support USE flag.  Is it needed now?
Date: Thu, 07 Oct 2010 18:15:06 -0500	[thread overview]
Message-ID: <4CAE547A.7030301@gmail.com> (raw)
In-Reply-To: <i8liq0$23r$2@dough.gmane.org>

Nikos Chantziaras wrote:
> On 10/08/2010 01:24 AM, Dale wrote:
>> Peter Humphrey wrote:
>>> On Thursday 07 October 2010 20:40:32 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.
>>> I have KDE-4.5.2 here. I get this:
>>>
>>> $ USE=-qt3support emerge -upDvN world
>>>
>>> These are the packages that would be merged, in order:
>>>
>>> Calculating dependencies ... done!
>>>
>>> emerge: there are no ebuilds built with USE flags to satisfy ">=x11-
>>> libs/qt-sql-4.6.3:4[qt3support]".
>>> !!! One of the following packages is required to complete your request:
>>> - x11-libs/qt-sql-4.6.3-r2 (Change USE: +qt3support)
>>> (dependency required by "kde-base/kfilereplace-4.5.2" [installed])
>>> (dependency required by "kde-base/kdewebdev-meta-4.5.2" [installed])
>>> (dependency required by "@selected")
>>> (dependency required by "@world" [argument])
>>>
>>> So it looks as though I at least can't get rid of it.
>>>
>>
>> It also looks like I can't get rid of it. lol I guess it will have to
>> stay, for now anyway.
>
> One thing I don't get is why this seems to worry you.  I don't see you 
> complaining about packages needing the "libsamplerate" or "opengl" USE 
> flags...  :-P
>

I don't get blocks from those tho.  That's why it bugs me.  Funny thing 
is, when I ran emerge again, no blocks.  I'm not sure how that worked.  
I guess it wanted me to ask a question on the mailing list.  Everything 
seems to be emerging just fine now.  Then again, it's not finished yet 
so there is still time for trouble.  ;-)

Dale

:-)  :-)



  reply	other threads:[~2010-10-07 23: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
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 [this message]
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=4CAE547A.7030301@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