Due to an issue with the logic in how the dependency graph is generated, doing scripts/ bootstrap.sh -f can pull down xfree if the user has edited his use flags sufficiently. Reproducible: Always Steps to Reproduce: 1. follow installation instructions up until just before scripts/bootstrap.sh 2. edit /etc/make.conf to have USE="*". 3. runu scripts/bootstrap.sh -f Actual Results: lots of packages (notably xfree) are downloaded. Expected Results: just download the source I need to bootstrap. (Note that xfree is *not* compiled, only downloaded.) This is due to the way that the script tells emerge to download the packages. Line 199 of bootstrap.sh sets USE to be whatever was in make.conf, plus "bootstrap". Then at line 200 texinfo, gettext, and binutils are built (ie, downloaded), which pulls in xfree. XFree is ultimately pulled in by portage, though, which would have been already up-to-date, had the user been compiling. I guess I'd suggest that portage should be pulled up to the newest version, even with "-f", but I don't know how strict the "-f means download it and don't compile a thing" contract is. I'm reporting this as minor as a user who's edited make.conf to have those cflags is going to have to pull down the packages at some point anyway, and a fix is just to do `USE="-* bootstrap build" emerge portage`.
can't assign to two people simultaneously...
this is probably related to the python some how pulling in X bug
I added a fix to xfree-4.3.0-r6 to work around an extended circular dependency between it and pam, might be worth testing this again with -r6 and USE=-pam.
should be OK now ...
