Hi again all,<br><br>Still relating to keyworded packages, why doesn't this work?<br><br>miguel@feynman ~ $ fgrep KEYWORD /usr/portage/dev-java/sun-jdk/sun-jdk-1.5.0.06.ebuild <br>KEYWORDS=&quot;~x86 ~amd64 -*&quot;<br>miguel@feynman
 ~ $ sudo fgrep sun-jdk /etc/portage/package.unmask<br>&gt;=dev-java/sun-jdk-1.5.0<br>miguel@feynman ~ $ sudo fgrep sun-jdk /etc/portage/package.keywords <br>dev-java/sun-jdk ~amd64<br>miguel@feynman ~ $ emerge sun-jdk -pv
<br><br>These are the packages that I would merge, in order:<br><br>Calculating dependencies&nbsp;&nbsp; <br>!!! All ebuilds that could satisfy &quot;sun-jdk&quot; have been masked.<br>!!! One of the following masked packages is required to complete your request:
<br>- dev-java/sun-jdk-1.5.0.06 (masked by: package.mask, ~amd64 keyword)<br><br><br>or this:<br>trying to emerge GCC 4.0.2<br>----<br>miguel@feynman ~ $ sudo fgrep gcc /etc/portage/package.*<br>/etc/portage/package.keywords:# gcc4
<br>/etc/portage/package.keywords:sys-devel/gcc -*<br>/etc/portage/package.unmask:=sys-devel/gcc-4.0.2-r2<br>miguel@feynman ~ $ sudo fgrep KEYWORDS /usr/portage/sys-devel/gcc/gcc-4.0.2-r2.ebuild <br>KEYWORDS=&quot;-*&quot;
<br>miguel@feynman ~ $ emerge gcc -pv<br><br>These are the packages that I would merge, in order:<br><br>Calculating dependencies ...done!<br>[ebuild&nbsp;&nbsp; R&nbsp;&nbsp; ] sys-devel/gcc-3.4.4-r1&nbsp; (-altivec) -bootstrap -boundschecking* -build +fortran -gcj +gtk -hardened -ip28 -mudflap (-multilib) -multislot (-n32) (-n64) +nls -nocxx -nopie -nossp -objc -objc-gc -vanilla 46 kB 
<br><br>Total size of downloads: 46 kB<br>miguel@feynman ~ $ ACCEPT_KEYWORDS=&quot;-*&quot; emerge =sys-devel/gcc-4.0.2-r2 -pv<br><br>These are the packages that I would merge, in order:<br><br>Calculating dependencies&nbsp;&nbsp; 
<br>!!! All ebuilds that could satisfy &quot;=sys-devel/gcc-4.0.2-r2&quot; have been masked.<br>!!! One of the following masked packages is required to complete your request:<br>- sys-devel/gcc-4.0.2-r2 (masked by: -* keyword)
<br><br>For more information, see MASKED PACKAGES section in the emerge man page or <br>refer to the Gentoo Handbook.<br><br>miguel@feynman ~ $ emerge =sys-devel/gcc-4.0.2-r2 -pv<br><br>These are the packages that I would merge, in order:
<br><br>Calculating dependencies&nbsp;&nbsp; <br>!!! All ebuilds that could satisfy &quot;=sys-devel/gcc-4.0.2-r2&quot; have been masked.<br>!!! One of the following masked packages is required to complete your request:<br>- sys-devel/gcc-
4.0.2-r2 (masked by: -* keyword)<br><br>For more information, see MASKED PACKAGES section in the emerge man page or <br>refer to the Gentoo Handbook.<br><br><br><br><div><span class="gmail_quote">On 12/23/05, <b class="gmail_sendername">
Miguel Filipe</b> &lt;<a href="mailto:miguel.filipe@...">miguel.filipe@...</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br><br>I've been trying to emerge <span id="st" name="st" class="st0">gcc</span> 4.0.2-r2, messing with /etc/portage/package.unmask &amp; /etc/portage/package.keywords <br>without success..<br><br>the portage man page says that if a package has -* is know to be broken on all arches otherwise mentioned.
<br>So is 4.0.1, 4.0.0, 4.1-snapshot..<br><br>I would expect it to be at least marked unstable &quot;~<span id="st" name="st" class="st0">amd64</span> ..&quot;<br><br><span id="st" name="st" class="st0">gentoo</span> seems to have major problems in keeping up with the public releases.. its starting to look like debian stable....
<br>also.. I don't see the point in having 3 types of tags: stable, unstable, broken.. maybe the same point of (stable, testing, unstable.. ala debian)<br><br>Nevermind, basically, I'm using <span id="st" name="st" class="st0">
gentoo</span> since 1.0rc6 and starting to be disapointed by the slowness of having fresh software available..
<br><br>gnome 2.12 came out 7 of september, maybe when gnome 2.14 is out I can find it keyworded &quot;<span id="st" name="st" class="st0">amd64</span>&quot;..<br><br>In conclusion, package mantainance needs a new organizational way to scale..
<br>Or should I simply move to ~<span id="st" name="st" class="st0">amd64</span>, just like any debian user sets its system to testing without thinking twice, just after the install.
<br><br>Best regards,<br clear="all"><span class="sg"><br>-- <br>Miguel Sousa Filipe

</span></blockquote></div><br><br clear="all"><br>-- <br>Miguel Sousa Filipe