-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/13/2014 08:20 PM, Peter Humphrey wrote: > On Monday 14 Apr 2014 00:30:44 Alan McKinnon wrote: > >> A proper answer involves posting the full verbose output of those emerge >> commands. > > OK. Attached; list and listk are as in my first message. > >> Without that we can only guess. My guess is that USE is different >> between your Atom and your build host, so using -k causes a different >> set of package deps to be pulled in. > > I've checked - for the umpteenth time - that package.use, package.keywords > and > package.mask are identical; also the portage profile and the world file. And > here are the differences between the two make.confs (portage.serv is the > Atom's > etc/portage and /etc/portage is the build host's):
The real answer is almost certainly dynamic-deps. The binary packages store the deps from BUILD time, while when you are installing things live, it allows the current ebuilds to update the deps even for installed packages. That means, after you install a package, if the deps in the ebuild are changed, portage will take that into account for source builds, but binary packages are LOCKED to the deps from the time they were built. Why dynamic-deps aren't available no matter what? Now that's a great question... - -Zero > > # diff portage.serv/make.conf /etc/portage/make.conf > 8c8 > < FEATURES="parallel-fetch userfetch" > --- >> FEATURES="buildpkg parallel-fetch userfetch" > 10c10 > < ftp_proxy="ftp://localhost:8080/"; > --- >> ftp_proxy="ftp://serv.prhnet:8080/"; > 14c14 > < http_proxy="http://localhost:8080/"; > --- >> http_proxy="http://serv.prhnet:8080/"; > 17c17 > < MAKEOPTS="-j3" > --- >> MAKEOPTS="-j5" > 24c24,25 > < SYNC="rsync://rsync.uk.gentoo.org/gentoo-portage" > --- >> SYNC="rsync://serv.prhnet/gentoo-portage" > > The machine serv.prhnet is a portage mirror for the rest of the LAN (it's the > Atom box); besides rsyncd it runs http-replicator listening to port 8080 to > serve the distfiles etc. Sometimes I have to think uncomfortably hard to > remember what's where, doing what to whom :-( > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTS0yLAAoJEKXdFCfdEflKOQIP/3RSALd4/ArvT9nFN3IzPjHT zVw9iimHMTOOeec4c4dhw6URCMNlOzeA2XL4cAdhiPM+ufHdJUWuR67tu78qD44S /p9UjBppBU2pTjpD/b0XcXXoER+D0uLmcnOzV4AZ0aTxVic1mYGR2PUnzFmZGYYd /+EM8ohTyiDyS9AANSzkqZsMS0NQpfmvVy3aqL6CjZt7zG92IOAYfXFysedh4Y7p aOordofyUXdMsooiajM9KKF5kgyUW/S0OuS6yAncWAgb38EqXlrwgbqQlLbvZaDp WSYkQy9HGfRxgNP3K2kEWJOrfjxQz/NoFwffaaPcgFPRRQ1SN9g7LkheZtCYhhV+ VAUXDjMk3NswcS36hiVqPqb87/XFlowkuqyjP/xCD0GdotY8CYblhr3lpFXZ/ucL VE6IpHRXd+JknK3h2N57MIbkxReW3KKBJ6TWnZBcVYsWcnu0gTf40babpzYvmVz6 dBAZ9ID/8BAkIUCdLsQcGPNcl1VUOMcJC19S7RZLg5sbX6pwvwlGmFuz5Kqchx3L W53e7js0c1PnWp505vPGnvfmXuYGQapRJ1JUQy6ERsST3y7DeWYn3gR0sSnp4VX2 9ymJHUytULUX51fc9YUbWTJfrG02J3j3kycF6PRz6M9BrBBXnNsQQ4HJaaBqTfrr 9l9gCfTtQAJcRuF21WvW =9tei -----END PGP SIGNATURE-----
