portage-2.0.49-r20 determine glibc subversion by, if test "$VERSION" = 'libc.so.6' ; then echo -n 'Checking glibc subversion... ' tmp="$(ldd /usr/bin/* 2>/dev/null | grep libc.so | tail -n 1)" LibcPath=`expr "$tmp" : '[^/]*\(/[^ ]*\)'` . . . when 2.0.50-pre9 do this as, tmp="`ldd bin/sh | grep libc.so 2>/dev/null `" ldd /usr/bin/* takes too much time to finish. maybe it's worse using head -n 1 or just like 2.0.50's Reproducible: Always Steps to Reproduce: 1. 2. 3.
That's very subjective. It's a fix to a potential problem, and it shouldn't be that big of a deal as you don't have reason to be repeatedly merging portage, as far as I'm aware.
yes but some people watch it and think 'oh no, portage froze' and then file a bug or, for some mildly-loaded systems that can easily take over a minute to complete ... i dont think thats really a valid answer when theres easy alternatives ... (1) use /usr/include/features.h ala autofoo style (2) quickly compile a test.c which is 'int main(){return 0;}' and ldd that
Good idea! Anyway, there should be added some warning at least so people won't give up waiting (like I did)... Radek
Fixed in cvs.
supposed to be fixed in 2.0.50 which is stable now. If this bug is not fixed please reopen.
