1 |
Hi again all, |
2 |
|
3 |
Still relating to keyworded packages, why doesn't this work? |
4 |
|
5 |
miguel@feynman ~ $ fgrep KEYWORD /usr/portage/dev-java/sun-jdk/sun- |
6 |
jdk-1.5.0.06.ebuild |
7 |
KEYWORDS="~x86 ~amd64 -*" |
8 |
miguel@feynman ~ $ sudo fgrep sun-jdk /etc/portage/package.unmask |
9 |
>=dev-java/sun-jdk-1.5.0 |
10 |
miguel@feynman ~ $ sudo fgrep sun-jdk /etc/portage/package.keywords |
11 |
dev-java/sun-jdk ~amd64 |
12 |
miguel@feynman ~ $ emerge sun-jdk -pv |
13 |
|
14 |
These are the packages that I would merge, in order: |
15 |
|
16 |
Calculating dependencies |
17 |
!!! All ebuilds that could satisfy "sun-jdk" have been masked. |
18 |
!!! One of the following masked packages is required to complete your |
19 |
request: |
20 |
- dev-java/sun-jdk-1.5.0.06 (masked by: package.mask, ~amd64 keyword) |
21 |
|
22 |
|
23 |
or this: |
24 |
trying to emerge GCC 4.0.2 |
25 |
---- |
26 |
miguel@feynman ~ $ sudo fgrep gcc /etc/portage/package.* |
27 |
/etc/portage/package.keywords:# gcc4 |
28 |
/etc/portage/package.keywords:sys-devel/gcc -* |
29 |
/etc/portage/package.unmask:=sys-devel/gcc-4.0.2-r2 |
30 |
miguel@feynman ~ $ sudo fgrep KEYWORDS /usr/portage/sys-devel/gcc/gcc- |
31 |
4.0.2-r2.ebuild |
32 |
KEYWORDS="-*" |
33 |
miguel@feynman ~ $ emerge gcc -pv |
34 |
|
35 |
These are the packages that I would merge, in order: |
36 |
|
37 |
Calculating dependencies ...done! |
38 |
[ebuild R ] sys-devel/gcc-3.4.4-r1 (-altivec) -bootstrap |
39 |
-boundschecking* -build +fortran -gcj +gtk -hardened -ip28 -mudflap |
40 |
(-multilib) -multislot (-n32) (-n64) +nls -nocxx -nopie -nossp -objc |
41 |
-objc-gc -vanilla 46 kB |
42 |
|
43 |
Total size of downloads: 46 kB |
44 |
miguel@feynman ~ $ ACCEPT_KEYWORDS="-*" emerge =sys-devel/gcc-4.0.2-r2 -pv |
45 |
|
46 |
These are the packages that I would merge, in order: |
47 |
|
48 |
Calculating dependencies |
49 |
!!! All ebuilds that could satisfy "=sys-devel/gcc-4.0.2-r2" have been |
50 |
masked. |
51 |
!!! One of the following masked packages is required to complete your |
52 |
request: |
53 |
- sys-devel/gcc-4.0.2-r2 (masked by: -* keyword) |
54 |
|
55 |
For more information, see MASKED PACKAGES section in the emerge man page or |
56 |
refer to the Gentoo Handbook. |
57 |
|
58 |
miguel@feynman ~ $ emerge =sys-devel/gcc-4.0.2-r2 -pv |
59 |
|
60 |
These are the packages that I would merge, in order: |
61 |
|
62 |
Calculating dependencies |
63 |
!!! All ebuilds that could satisfy "=sys-devel/gcc-4.0.2-r2" have been |
64 |
masked. |
65 |
!!! One of the following masked packages is required to complete your |
66 |
request: |
67 |
- sys-devel/gcc-4.0.2-r2 (masked by: -* keyword) |
68 |
|
69 |
For more information, see MASKED PACKAGES section in the emerge man page or |
70 |
refer to the Gentoo Handbook. |
71 |
|
72 |
|
73 |
|
74 |
On 12/23/05, Miguel Filipe <miguel.filipe@×××××.com> wrote: |
75 |
> |
76 |
> Hi all, |
77 |
> |
78 |
> I've been trying to emerge gcc 4.0.2-r2, messing with |
79 |
> /etc/portage/package.unmask & /etc/portage/package.keywords |
80 |
> without success.. |
81 |
> |
82 |
> the portage man page says that if a package has -* is know to be broken on |
83 |
> all arches otherwise mentioned. |
84 |
> So is 4.0.1, 4.0.0, 4.1-snapshot.. |
85 |
> |
86 |
> I would expect it to be at least marked unstable "~amd64 .." |
87 |
> |
88 |
> gentoo seems to have major problems in keeping up with the public |
89 |
> releases.. its starting to look like debian stable.... |
90 |
> also.. I don't see the point in having 3 types of tags: stable, unstable, |
91 |
> broken.. maybe the same point of (stable, testing, unstable.. ala debian) |
92 |
> |
93 |
> Nevermind, basically, I'm using gentoo since 1.0rc6 and starting to be |
94 |
> disapointed by the slowness of having fresh software available.. |
95 |
> |
96 |
> gnome 2.12 came out 7 of september, maybe when gnome 2.14 is out I can |
97 |
> find it keyworded "amd64".. |
98 |
> |
99 |
> In conclusion, package mantainance needs a new organizational way to |
100 |
> scale.. |
101 |
> Or should I simply move to ~amd64, just like any debian user sets its |
102 |
> system to testing without thinking twice, just after the install. |
103 |
> |
104 |
> Best regards, |
105 |
> |
106 |
> -- |
107 |
> Miguel Sousa Filipe |
108 |
|
109 |
|
110 |
|
111 |
|
112 |
-- |
113 |
Miguel Sousa Filipe |