1 |
On Thursday 16 March 2006 23:03, James wrote: |
2 |
> Dmitry S. Makovey <dmitry <at> athabascau.ca> writes: |
3 |
> > since packages you use (I assume KDE etc.) are not using qt4 (i.e. |
4 |
> > require specifically qt3 branch) portage doesn't find any reasons to |
5 |
> > bump version of qt. AFAIR Qt is a slotted package and you can safely |
6 |
> > go ahead and do |
7 |
> > emerge =x11-libs/qt-4.1.1 |
8 |
> > but you packages wouldn't use it. |
9 |
> |
10 |
> Ok this kinda makes sense. But what exactly is a 'slotted package', |
11 |
|
12 |
Slotted means that several versions of a package can coexist at the same |
13 |
system. In the case of qt version 3 goes into /usr/qt/3 and version 4 goes |
14 |
into /usr/qt/4. |
15 |
|
16 |
> how do I determine when a packages is slotted, and where do I read |
17 |
> more about 'slotted'? |
18 |
|
19 |
Have a look at 'man emerge' |
20 |
# emerge -vp qt |
21 |
|
22 |
These are the packages that would be merged, in order: |
23 |
|
24 |
Calculating dependencies... done! |
25 |
[ebuild NS ] x11-libs/qt-4.1.1 USE="..." 27,110 kB |
26 |
^^^ |
27 |
The 'S' means that it is slotted. |
28 |
|
29 |
On Thursday 16 March 2006 20:11, James wrote: |
30 |
> I really confused as this is not very clear what the hardmasked, testing |
31 |
> and stable versions of QT........? |
32 |
> |
33 |
> I've been told that QT 4 is 'very young' which I interpret as unstable |
34 |
> and buggy. How do I tell if qt-4.1.1 is hard masked or testing.... |
35 |
> as I've never seen this before. |
36 |
|
37 |
I would recommend app-portage/eix as it gives a clear overview of the |
38 |
available versions of any package. |
39 |
|
40 |
# eix -e qt |
41 |
* x11-libs/qt |
42 |
Available versions: 3.3.4-r8 ~3.3.4-r9 [M]3.3.5 [M]3.3.5-r1 4.1.0-r1 |
43 |
4.1.0-r2 4.1.1 |
44 |
Installed: 3.3.4-r8 |
45 |
Homepage: http://www.trolltech.com/ |
46 |
Description: The Qt toolkit is a comprehensive C++ application |
47 |
development framework. |
48 |
|
49 |
Versions that are prefixed by [M] are hard masked usually because they are |
50 |
broken. They should not be unmasked without knowing why they were originally |
51 |
masked. Versions prefixed by a ~ are masked by ~ARCH i.e. testing and can be |
52 |
used by adding them to package.keyword. eix respects package.* an hence |
53 |
4.1.0-r1 is shown as stable because of this: |
54 |
|
55 |
# grep x11-libs/qt /etc/portage/package.keywords |
56 |
=x11-libs/qt-4.1* ~x86 |
57 |
|
58 |
As you can see you can specify versions to unmask if you want a testing |
59 |
version of qt-4.1* but stable for any other version. This is explained in |
60 |
'man portage'. |
61 |
|
62 |
To see why a package is hard masked you have to look in the package.mask |
63 |
files. |
64 |
|
65 |
Packages are masked on several levels. Both general and profile specific. On |
66 |
my system I am using the default-linux/x86/2006.0 profile. |
67 |
|
68 |
# ls -ld /etc/make.profile |
69 |
lrwxrwxrwx 1 root root 48 Mar 10 02:02 /etc/make.profile |
70 |
-> ../usr/portage/profiles/default-linux/x86/2006.0 |
71 |
|
72 |
Therefore packages on my system might be masked in the following locations |
73 |
(note that not all of those files actually exist because no packages are hard |
74 |
masked on some of those levels. Still these are the locations where portage |
75 |
will look.): |
76 |
/usr/portage/profiles/default-linux/x86/2006.0/package.mask |
77 |
/usr/portage/profiles/default-linux/x86/package.mask |
78 |
/usr/portage/profiles/default-linux/package.mask |
79 |
/usr/portage/profiles/package.mask |
80 |
|
81 |
And the reason why qt-3.3.5 is hard masked: |
82 |
# grep -A 2 Qt /usr/portage/profiles/package.mask |
83 |
# Qt-3.3.5 causes a lot of compilation failures. |
84 |
# See bug #106402. |
85 |
~x11-libs/qt-3.3.5 |
86 |
|
87 |
But qt-4 is not hard masked so it should be working or at least it won't break |
88 |
anything. ;) |
89 |
|
90 |
HtH |
91 |
|
92 |
-- |
93 |
Bo Andresen |
94 |
-- |
95 |
gentoo-user@g.o mailing list |