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: Thu, 11 Feb 2010 00:25:03
Message-Id: 201002110124.25135.volkerarmin@googlemail.com
In Reply to: Re: [gentoo-user] Qt3 deprecated, but Qt4 still not x86 (only ~x86)??? by Mark Knecht
1 On Donnerstag 11 Februar 2010, Mark Knecht wrote:
2 > On Wed, Feb 10, 2010 at 11:40 AM, Volker Armin Hemmann
3 > <volkerarmin@××××××××××.com> wrote:
4 > <SNIP>
5 >
6 > >> Again, I cannot see the 0.22 gives me anything I care about but
7 > >> there's no way to know until I commit to making the change.
8 > >>
9 > >> Cheers,
10 > >> Mark
11 > >
12 > > if everything works, why are you even bothering with updates? Why do you
13 > > care at all that qt3 is going away?
14 > >
15 > > but as I told you, the solution is quickpkg.
16 > >
17 > > And for quickly deploying packages:
18 > > buidpkg
19 > > BINHOST.
20 > >
21 > > have a look at man emerge, man make.conf
22 >
23 > Volker,
24 > Thanks. I've not used quickpkg before but it seems like a very good
25 > short term solution.
26 >
27 > If I understand correctly I'd do something more or less like this?
28 >
29 > 1) quickpkg =qt-3.3.8xxxxxxx This creates the binary package and
30 > stores it in /usr/portage/package. I've done this step and the package
31 > is there.
32 >
33 > 2) emerge -C =qt-3.3.8xxxxx to remove the original. Easy when I do it.
34 >
35 > 3) emerge -pvg =qt-3.3.8b-r2 to get it to use the quickpkg version
36
37 no.
38
39 you are using -k not -g.
40
41 >
42 > This all seems to work but it complains a bit about PORTAGE_BINHOST
43 > not being set. As best I can tell that's only for using another
44 > machine to get the binary? Is that true? Is seems from these commands
45 > that it's finding the one I just made. Or is there a format for doing
46 > this and pointing at a local directory?
47 >
48 > firefly ~ # emerge -pvg =x11-libs/qt-3.3.8b-r2
49 >
50 > These are the packages that would be merged, in order:
51 >
52 > Calculating dependencies !!! PORTAGE_BINHOST unset, but use is requested.
53 > ... done!
54 > [binary R ] x11-libs/qt-3.3.8b-r2 USE="cups ipv6 mysql opengl
55 > -debug -doc -examples (-firebird) -immqt -immqt-bc -nas -nis -odbc
56 > -postgres -sqlite -xinerama"
57 >
58 > Total: 1 package (1 reinstall, 1 binary), Size of downloads: 0 kB
59 > firefly ~ # emerge -pv =x11-libs/qt-3.3.8b-r2
60 >
61 > These are the packages that would be merged, in order:
62 >
63 > Calculating dependencies... done!
64 > [ebuild R ] x11-libs/qt-3.3.8b-r2 USE="cups ipv6 mysql opengl
65 > -debug -doc -examples (-firebird) -immqt -immqt-bc -nas -nis -odbc
66 > -postgres -sqlite -xinerama" 0 kB
67 >
68 > Total: 1 package (1 reinstall), Size of downloads: 0 kB
69 > firefly ~ #
70
71 you get that message because you are telling portage to get that package from
72 BINHOST. That is great if you have one machine building packages and the rest
73 of your machines pulling them from the server and install them.
74
75 What you want/should/must use is -k = usepkg or -K = usepkgonly
76
77 Also, it is a wise decision to have the buildpkg option set in make.conf, if
78 you have a couple of gb to spare. That helps a lot in cases of bad updates,
79 filesystem damage, or the need to go back a version quickly for whatever
80 reasons.