| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Amit Dor-Shifer wrote: |
| 5 |
> When you say ut checks CHOST/keywording, where are those definitions |
| 6 |
> stored for the binary pkg? |
| 7 |
|
| 8 |
It's appended to the tail end of the tbz2, in xpak format (see `man |
| 9 |
5 xpak`). |
| 10 |
|
| 11 |
> I see one instance of CHOST in the 'Packages' index on the BINHOST. Is |
| 12 |
> that the variable emerge is comparing against? If not, where is it? the |
| 13 |
> tbz itself holds just the binaries. |
| 14 |
|
| 15 |
Yes, for remote packages, the Package index contains equivalent data |
| 16 |
to the actual xpak segments from the remote packages. The CHOST for |
| 17 |
individual packages is only shown in cases when it differs from the |
| 18 |
CHOST in the header of the Packages file. |
| 19 |
|
| 20 |
> Manually modifying a/m CHOST to 'ppc' didn't stop emerge from |
| 21 |
> successfully merging a package on an amd64 target (I've removed |
| 22 |
> /usr/portage/packages from target before emerging). |
| 23 |
|
| 24 |
The CHOST from your local configuration (typically from make.conf or |
| 25 |
inherited from your profile) is compared to the CHOST of the binary |
| 26 |
package. You can also use ACCEPT_CHOSTS if you want to accept more |
| 27 |
than one CHOST (see `man 5 make.conf`). |
| 28 |
- -- |
| 29 |
Thanks, |
| 30 |
Zac |
| 31 |
-----BEGIN PGP SIGNATURE----- |
| 32 |
Version: GnuPG v2.0.11 (GNU/Linux) |
| 33 |
|
| 34 |
iEYEARECAAYFAknsPqIACgkQ/ejvha5XGaNnEgCfVB8ricVhKBQY/S2g1aYLvpkT |
| 35 |
L2wAn3CtsAnFwJ0h/mArfdDJk4hMvNBD |
| 36 |
=AH2B |
| 37 |
-----END PGP SIGNATURE----- |
Archives