| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 04/13/2014 08:20 PM, Peter Humphrey wrote: |
| 5 |
> On Monday 14 Apr 2014 00:30:44 Alan McKinnon wrote: |
| 6 |
> |
| 7 |
>> A proper answer involves posting the full verbose output of those emerge |
| 8 |
>> commands. |
| 9 |
> |
| 10 |
> OK. Attached; list and listk are as in my first message. |
| 11 |
> |
| 12 |
>> Without that we can only guess. My guess is that USE is different |
| 13 |
>> between your Atom and your build host, so using -k causes a different |
| 14 |
>> set of package deps to be pulled in. |
| 15 |
> |
| 16 |
> I've checked - for the umpteenth time - that package.use, package.keywords and |
| 17 |
> package.mask are identical; also the portage profile and the world file. And |
| 18 |
> here are the differences between the two make.confs (portage.serv is the Atom's |
| 19 |
> etc/portage and /etc/portage is the build host's): |
| 20 |
|
| 21 |
The real answer is almost certainly dynamic-deps. The binary packages |
| 22 |
store the deps from BUILD time, while when you are installing things |
| 23 |
live, it allows the current ebuilds to update the deps even for |
| 24 |
installed packages. |
| 25 |
|
| 26 |
That means, after you install a package, if the deps in the ebuild are |
| 27 |
changed, portage will take that into account for source builds, but |
| 28 |
binary packages are LOCKED to the deps from the time they were built. |
| 29 |
|
| 30 |
Why dynamic-deps aren't available no matter what? Now that's a great |
| 31 |
question... |
| 32 |
|
| 33 |
- -Zero |
| 34 |
> |
| 35 |
> # diff portage.serv/make.conf /etc/portage/make.conf |
| 36 |
> 8c8 |
| 37 |
> < FEATURES="parallel-fetch userfetch" |
| 38 |
> --- |
| 39 |
>> FEATURES="buildpkg parallel-fetch userfetch" |
| 40 |
> 10c10 |
| 41 |
> < ftp_proxy="ftp://localhost:8080/" |
| 42 |
> --- |
| 43 |
>> ftp_proxy="ftp://serv.prhnet:8080/" |
| 44 |
> 14c14 |
| 45 |
> < http_proxy="http://localhost:8080/" |
| 46 |
> --- |
| 47 |
>> http_proxy="http://serv.prhnet:8080/" |
| 48 |
> 17c17 |
| 49 |
> < MAKEOPTS="-j3" |
| 50 |
> --- |
| 51 |
>> MAKEOPTS="-j5" |
| 52 |
> 24c24,25 |
| 53 |
> < SYNC="rsync://rsync.uk.gentoo.org/gentoo-portage" |
| 54 |
> --- |
| 55 |
>> SYNC="rsync://serv.prhnet/gentoo-portage" |
| 56 |
> |
| 57 |
> The machine serv.prhnet is a portage mirror for the rest of the LAN (it's the |
| 58 |
> Atom box); besides rsyncd it runs http-replicator listening to port 8080 to |
| 59 |
> serve the distfiles etc. Sometimes I have to think uncomfortably hard to |
| 60 |
> remember what's where, doing what to whom :-( |
| 61 |
> |
| 62 |
|
| 63 |
-----BEGIN PGP SIGNATURE----- |
| 64 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 65 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 66 |
|
| 67 |
iQIcBAEBAgAGBQJTS0yLAAoJEKXdFCfdEflKOQIP/3RSALd4/ArvT9nFN3IzPjHT |
| 68 |
zVw9iimHMTOOeec4c4dhw6URCMNlOzeA2XL4cAdhiPM+ufHdJUWuR67tu78qD44S |
| 69 |
/p9UjBppBU2pTjpD/b0XcXXoER+D0uLmcnOzV4AZ0aTxVic1mYGR2PUnzFmZGYYd |
| 70 |
/+EM8ohTyiDyS9AANSzkqZsMS0NQpfmvVy3aqL6CjZt7zG92IOAYfXFysedh4Y7p |
| 71 |
aOordofyUXdMsooiajM9KKF5kgyUW/S0OuS6yAncWAgb38EqXlrwgbqQlLbvZaDp |
| 72 |
WSYkQy9HGfRxgNP3K2kEWJOrfjxQz/NoFwffaaPcgFPRRQ1SN9g7LkheZtCYhhV+ |
| 73 |
VAUXDjMk3NswcS36hiVqPqb87/XFlowkuqyjP/xCD0GdotY8CYblhr3lpFXZ/ucL |
| 74 |
VE6IpHRXd+JknK3h2N57MIbkxReW3KKBJ6TWnZBcVYsWcnu0gTf40babpzYvmVz6 |
| 75 |
dBAZ9ID/8BAkIUCdLsQcGPNcl1VUOMcJC19S7RZLg5sbX6pwvwlGmFuz5Kqchx3L |
| 76 |
W53e7js0c1PnWp505vPGnvfmXuYGQapRJ1JUQy6ERsST3y7DeWYn3gR0sSnp4VX2 |
| 77 |
9ymJHUytULUX51fc9YUbWTJfrG02J3j3kycF6PRz6M9BrBBXnNsQQ4HJaaBqTfrr |
| 78 |
9l9gCfTtQAJcRuF21WvW |
| 79 |
=9tei |
| 80 |
-----END PGP SIGNATURE----- |
Archives