Gentoo Archives: gentoo-user

From: Volker Armin Hemmann <volkerarmin@××××××××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Qt3 deprecated, but Qt4 still not x86 (only ~x86)???
Date: Wed, 10 Feb 2010 19:41:56
Message-Id: 201002102040.59252.volkerarmin@googlemail.com
In Reply to: Re: [gentoo-user] Qt3 deprecated, but Qt4 still not x86 (only ~x86)??? by Mark Knecht
1 On Mittwoch 10 Februar 2010, Mark Knecht wrote:
2 > On Wed, Feb 10, 2010 at 10:46 AM, Neil Bothwick <neil@××××××××××.uk> wrote:
3 > > On Wed, 10 Feb 2010 09:30:19 -0800, Mark Knecht wrote:
4 > >> I seem to have them both installed with only my old version of MYthTV
5 > >> requiring qt-3.3.8
6 > >
7 > > That's easy then, switch to MythTV 0.22, it's much better :)
8 > >
9 > >
10 > > --
11 > > Neil Bothwick
12 >
13 > I don't care at all that it's much better. I care that what I have
14 > works and the family doesn't bother me.
15 >
16 > My Myth server is PowerPC based and so everytime I switch there's
17 > always things to relearn in terms of updating kernel and risks that
18 > others don't have.
19 >
20 > And I cannot update mythfrontend on my desktop machine without
21 > updating EVERY machine on the network to 0.22, so that's 2 desktops, 2
22 > dedicated machines hooked to TVs and the server. That's a lot of work
23 > just because someone decides they don't want to support it anymore.
24 >
25 > On the other hand, if the qt4 qt3-support works then I don't update
26 > from 0.21 at all.
27 >
28 > Again, I cannot see the 0.22 gives me anything I care about but
29 > there's no way to know until I commit to making the change.
30 >
31 > Cheers,
32 > Mark
33
34 if everything works, why are you even bothering with updates? Why do you care
35 at all that qt3 is going away?
36
37 but as I told you, the solution is quickpkg.
38
39 And for quickly deploying packages:
40 buidpkg
41 BINHOST.
42
43 have a look at man emerge, man make.conf

Replies

Subject Author
Re: [gentoo-user] Qt3 deprecated, but Qt4 still not x86 (only ~x86)??? Mark Knecht <markknecht@×××××.com>