@Python, do we want stuff to use virtualenv like this? Doesn't that risk fetching deps from www? checking for /usr/bin/python2.7... /usr/bin/python2.7 Creating Python environment New python executable in /var/tmp/portage/www-client/firefox-20.0.1/work/mozilla-release/obj-x86_64-unknown-linux-gnu/_virtualenv/bin/python2.7 Also creating executable in /var/tmp/portage/www-client/firefox-20.0.1/work/mozilla-release/obj-x86_64-unknown-linux-gnu/_virtualenv/bin/python Installing setuptools............done. Installing pip...............done. running build_ext building '_psutil_linux' extension creating build/temp.linux-x86_64-2.7 creating build/temp.linux-x86_64-2.7/psutil x86_64-pc-linux-gnu-gcc -pthread -fPIC -I/usr/include/python2.7 -c psutil/_psutil_linux.c -o build/temp.linux-x86_64-2.7/psutil/_psutil_linux.o creating build/lib.linux-x86_64-2.7 x86_64-pc-linux-gnu-gcc -pthread -shared build/temp.linux-x86_64-2.7/psutil/_psutil_linux.o -L/usr/lib64 -lpython2.7 -o build/lib.linux-x86_64-2.7/_psutil_linux.so building '_psutil_posix' extension x86_64-pc-linux-gnu-gcc -pthread -fPIC -I/usr/include/python2.7 -c psutil/_psutil_posix.c -o build/temp.linux-x86_64-2.7/psutil/_psutil_posix.o x86_64-pc-linux-gnu-gcc -pthread -shared build/temp.linux-x86_64-2.7/psutil/_psutil_posix.o -L/usr/lib64 -lpython2.7 -o build/lib.linux-x86_64-2.7/_psutil_posix.so copying build/lib.linux-x86_64-2.7/_psutil_linux.so -> copying build/lib.linux-x86_64-2.7/_psutil_posix.so ->
Being collection of hacks on top of autoconf 2.13, upstream build system of (most of) mozilla family simply has to be a mess. As gargantuan as those packages are, upstream is simply unwilling to take the effort needed to clean this up, as it would likely ended up rewriting this scheme from scratch.
Rafał, from reading upstream's blogs, it doesn't seem like they're "simply unwilling to take the effort needed to clean this up". Quite the contrary, they've been doing a bunch of stuff to make their build system faster and easier to use (though maybe less standard). I think they now use their own build tool, mach, which is written in Python, probably what they use the venv for. IIRC, virtualenv doesn't necessarily mean that stuff gets installed from www, but I haven't used it a whole lot. Does anyone else know?
@comment 2: see 5000_fix-title-backspace.patch from firefox patches tarball - unless I'm missing something, this problem is caused by upstream using autoconf 2.13; While an effort is indeed made, it's done by adding another layer of hacks. Not that I can't see some of their point - it's enough to look at transition problems mesa had recently (chances are it's not completely done yet, a few corner cases might still linger). On that note: bug 428460.
(In reply to comment #2) > IIRC, virtualenv doesn't necessarily mean that stuff gets installed from > www, but I haven't used it a whole lot. Does anyone else know? Yes, I know. That's why I'd like someone who has a better idea about it or more free time to check this.
updates?
If you feel I have closed your bug and it is still a current issue, please reopen and update it completely. We will not work bugs that have no ebuild in tree any longer or can not be reproduced with a current system. Thank You for your support and understanding The Mozilla Team
