| 1 |
Nikos Chantziaras wrote: |
| 2 |
> On 10/08/2010 02:17 AM, Dale wrote: |
| 3 |
>> Nikos Chantziaras wrote: |
| 4 |
>>> On 10/08/2010 01:14 AM, Dale wrote: |
| 5 |
>>>> Paul Hartman wrote: |
| 6 |
>>>>> On Thu, Oct 7, 2010 at 2:40 PM, Dale<rdalek1967@×××××.com> wrote: |
| 7 |
>>>>>> Hi, |
| 8 |
>>>>>> |
| 9 |
>>>>>> I have a question. I'm using KDE4, about to switch to 4.5.2. Do I |
| 10 |
>>>>>> need |
| 11 |
>>>>>> qt3support anymore? I'm talking about the USE flag qt3support. I run |
| 12 |
>>>>>> into |
| 13 |
>>>>>> blocks sometimes and I know KDE3 needed qt3. I'm just curious if I |
| 14 |
>>>>>> can get |
| 15 |
>>>>>> rid of this USE flag now. I only have KDE4 installed. No more KDE3 |
| 16 |
>>>>>> left |
| 17 |
>>>>>> that I know of. |
| 18 |
>>>>> Going along with what Alan said. qt3support does not use Qt 3 at all. |
| 19 |
>>>>> It just puts something like a Qt 3-compatible API into Qt 4, to make |
| 20 |
>>>>> porting Qt 3 to Qt 4 apps easier. It is largely insignifcant to you |
| 21 |
>>>>> (since it's not pulling in qt3 packages). |
| 22 |
>>>>> |
| 23 |
>>>>> If you have any packages that require this USE flag, their ebuild |
| 24 |
>>>>> will |
| 25 |
>>>>> require this USE flag. So disable it, emerge --deep --newuse world |
| 26 |
>>>>> and |
| 27 |
>>>>> see if it complains. If it does, re-enable and continue life with |
| 28 |
>>>>> qt3support as if nothing ever happened. :) |
| 29 |
>>>>> |
| 30 |
>>>> |
| 31 |
>>>> Just picking the last message to reply to so this is for everyone who |
| 32 |
>>>> has chimed in so far. |
| 33 |
>>>> |
| 34 |
>>>> I may remove the USE flag and just see what blows up. I may copy over |
| 35 |
>>>> some binaries so that I can just use -k and not have to wait on the |
| 36 |
>>>> compiles. I would think if I remove it that something would pitch all |
| 37 |
>>>> holy hell about it if it has to have it. I'm sure it would be |
| 38 |
>>>> caught at |
| 39 |
>>>> some point and I would know it then for sure. |
| 40 |
>>>> |
| 41 |
>>>> I'm not sure if I have anything on here that must have qt3support. Is |
| 42 |
>>>> there a way to know for sure? Maybe some obscure command that I am not |
| 43 |
>>>> familiar with? |
| 44 |
>>> |
| 45 |
>>> revdep-rebuild will help. The qt3support USE flag is nothing magical; |
| 46 |
>>> it simply pulls the "x11-libs/qt-qt3support" as a dependency. This |
| 47 |
>>> package installs the /usr/lib/qt4/libQt3Support.so.* libraries. So if |
| 48 |
>>> you have binaries that try to load this lib, revdep-rebuild will find |
| 49 |
>>> them. |
| 50 |
>>> |
| 51 |
>>> And in general, if *any* binary you try to run aborts with something |
| 52 |
>>> like "libQt3Support.so not found" or similar, then you know it needs |
| 53 |
>>> qt3support. |
| 54 |
>>> |
| 55 |
>>> |
| 56 |
>> |
| 57 |
>> I didn't want to remove it and recompile just to find out KDE won't work |
| 58 |
>> anymore. That would be . . . bad. lol |
| 59 |
> |
| 60 |
> There's the "rm" command, and then there's "mv". |
| 61 |
> |
| 62 |
|
| 63 |
But I would still have to recompile again with the qt3support flag if it |
| 64 |
messed up badly. On this machine, that takes time. During that time, I |
| 65 |
may not have KDE at all. I did that when I made a mistake a while |
| 66 |
back. About 12 hours with no GUI. That was with some packages being |
| 67 |
binary and using -k. If I have to recompile them all, it would take |
| 68 |
longer still. |
| 69 |
|
| 70 |
Not something I want to repeat. |
| 71 |
|
| 72 |
Dale |
| 73 |
|
| 74 |
:-) :-) |
Archives