It's not as easy as I thought to find that out. After running unstable
for a while I had so many that it was hard to know what was stopping wine
and winex from working ( they worked fine on my stable partition ).
So I commented ACCEPT_KEYWORDS="~x86" in my make.conf and did `emerge
world -u`. It took several hours and now I'm going to be more selective
with ACCEPT_KEYWORDS="~x86". Wine and winex are working again.
This is the script I now use to keep track of the unstable builds:
#===================================================================
#!/bin/sh
#
# /usr/local/bin/list-tested
# Need to run as root, for copying ebuilds: e.g. `sudo list-tested`
# Lists ebuilds installed with 'ACCEPT_KEYWORDS="~x86"'
#
# Peter Ruskin <[EMAIL PROTECTED]>
LOGFILE=/usr/local/var/log/list-tested-$(date +%Y-%m-%d-%H%M).log
unset RESULT1
unset RESULT2
RESULT1=$(mktemp $0.XXXXXX)
RESULT2=$(mktemp $0.XXXXXX)
# For any '~x86' ebuilds in /var/db/pkg, first make sure they are
# the latest ebuild for that version (changed KEYWORDS don't get
# updated)
grep -R '~x86' /var/db/pkg/*/*/*.ebuild | grep -Rv '#' | cut -d/ -f1-6 >
$RESULT1
for a in $(cat $RESULT1); do
cd $a
file=$(echo $a | cut -d/ -f6).ebuild
[ -e /usr/portage/*/*/$file ] && cp /usr/portage/*/*/$file ./$file
done
grep -R '~x86' /var/db/pkg/*/*/*.ebuild | grep -Rv '#' | cut -d/ -f5-6 >
$RESULT2
touch $LOGFILE
echo "These ebuilds were installed using 'ACCEPT_KEYWORDS=\"~x86\"':"
echo "These ebuilds were installed using 'ACCEPT_KEYWORDS=\"~x86\"':" \
> $LOGFILE
cat $RESULT2 | tee -a $LOGFILE
# Clean up
rm -f $RESULT1 $RESULT2
#===================================================================
Maybe it will be of help to someone?
Peter
--
Gentoo-1.4.2.8 Unstable. KDE: 3.1.1 Qt: 3.1.0
AMD Athlon(tm) XP 2200+ 768MB. Kernel: 2.4.20-xfs-r2. GCC 3.2.2
--
[EMAIL PROTECTED] mailing list
