CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O3 -mmmx -m3dnow -mfpmath=sse -pipe" CXXFLAGS="${CFLAGS}" MAKEOPTS="-j2" ACCEPT_KEYWORDS="~x86" USE="aalib bonobo cups doc dvd esd evo fbcon flash gb gd ghostscript gtkhtml hpijs innodb mbox motifnocardbus mysql nls nocardbus odbc perl postgres samba slp sse tcltk tetex tiff xml"
when you say "tested OK" what exactly do you mean by that?
It means that I have ACCEPT_KEYWORDS="~x86" in my make.conf; I emerged the thing; tried it and it worked fine. I thought feedback (positive and negative) was required on these ~ ebuilds (testing/unstable) ... maybe bugzilla is the wrong place? It's awkward for me too, to provide individual ebuild feedback. I have made a script that interrogates the system and reports what ebuilds have been installed with "~x86". Current output is: $ list-tested These ebuilds were installed using 'ACCEPT_KEYWORDS="~x86"': gkrellm-2.1.0 portagemaster-0.2.0 tmpwatch-2.8.4 file-roller-2.0.4 cdrdao-1.1.7-r1 k3b-0.7.3 gpgme-0.3.12 gvim-6.1-r3 vim-6.1-r16 angband-3.0.1 lbreakout2-2.3.5 endeavour-2.1.20 gramps-0.8.0 scribus-0.8 ghostview-1.5-r1 mysql-3.23.53 sqlite-2.7.3 ant-1.5.1-r1 swig-1.3.16 aterm-1.6.7 libusb-0.1.6a kdbg-1.2.6 gnome-panel-2.0.10 gnome-panel-1.4.2-r1 mc-4.6.0_pre1-r3 gliv-1.6 gqview-1.1.6 graphviz-1.8.10 gwenview-0.15.1 sodipodi-0.27 xv-3.10a-r3 libpng-1.2.5 alsa-xmms-0.9.7 xmms-midi-0.03 alsa-driver-0.9.0_rc5 alsa-utils-0.9.0_rc5 ripperx-2.4 mplayer-0.90_pre9 nvoption-0_alpha-r1 nfs-utils-1.0.1 libfwbuilder-0.10.11 libpcap-0.7.1-r1 firestarter-0.9.0 knetfilter-3.0.3 rdate-990821-r1 whois-4.5.31 hpijs-1.2.2-r1 opera-static-6.1 hotplug-20020826 lm_sensors-2.6.5 mondo-0.9 syscriptor-1.5.12 xinetd-2.3.9 libast-0.5 fluxconf-0.9.0 xscreensaver-4.06-r2 gkrellaclock-0.3.2 eterm-0.9.2-r1 fluxbox-0.1.12-r2 icewm-1.2.3_pre1-r1 metacity-2.4.3 openbox-2.2.0-r1 Who could be interested in this? Here's the script: #!/bin/sh # # list-tested # # Lists ebuilds installed with 'ACCEPT_KEYWORDS="~x86"' # # Peter Ruskin <aoyu93@dsl.pipex.com> # Sort the world file WORLD=/var/cache/edb/world SORTEDWORLD=$(mktemp $0.XXXXXX) sort -u $WORLD > $SORTEDWORLD # Make ~x86 list from cache in same format as world file TESTING=$(mktemp $0.XXXXXX) grep -r '~x86' /var/cache/edb/dep/* | cut -d/ -f6-7 | cut -d: -f1 | cut -d. -f1 | cut -d- -f1-3 | sed s/-[0-9].*//g > $TESTING SORTEDTESTING=$(mktemp $0.XXXXXX) sort -u $TESTING > $SORTEDTESTING # Report matches and add versions RESULT1=$(mktemp $0.XXXXXX) RESULT2=$(mktemp $0.XXXXXX) comm -12 $SORTEDWORLD $SORTEDTESTING > $RESULT1 cat $RESULT1 | cut -d/ -f2 > $RESULT2 echo "These ebuilds were installed using 'ACCEPT_KEYWORDS=\"~x86\"':" cat $RESULT2 | xargs epm -q # Clean up rm $SORTEDWORLD $TESTING $SORTEDTESTING $RESULT1 $RESULT2
sorry, my question was a bit unclear. a lot of time people just compile things and report is as OK and stable. The real stability is in that AND in its use..
Thanks for your report, the preferred way for this is most likely going to be the Gentoo Stable project : gentoo-stable.iq-computing.de . Unmasked now.
