| 1 |
On Tuesday 29 November 2005 01:23, Mark Knecht wrote: |
| 2 |
> On another list, music based, I was told by someone that using both |
| 3 |
> ~x86 and ~AMD64 on the same system is incorrect by design. I have no |
| 4 |
> reason to not believe him but I seem to have missed this point when I |
| 5 |
> was building this system. |
| 6 |
> |
| 7 |
> Can someone clarify if this is the case? If so, what is the |
| 8 |
> recommended action for me to take at this point? |
| 9 |
|
| 10 |
It depends on the profile you are currently using. |
| 11 |
|
| 12 |
# ls -l /etc/make.profile |
| 13 |
lrwxrwxrwx 1 root root 50 mei 11 2005 /etc/make.profile |
| 14 |
-> ../usr/portage/profiles/default-linux/amd64/2005.0 |
| 15 |
|
| 16 |
As you can see my system is using the amd64 profile version 2005.0 |
| 17 |
That gives ACCEPT_KEYWORDS a default value of "amd64" |
| 18 |
If I want to run packages marked unstable for amd64 I would change the |
| 19 |
ACCEPT_KEYWORDS value to "~amd64" in /etc/make.conf |
| 20 |
|
| 21 |
ACCEPT_KEYWORDS decides which package versions portage should use when merging |
| 22 |
something. |
| 23 |
Each ebuild has a KEYWORDS variable, it lists all the arches that can use that |
| 24 |
version of a package. |
| 25 |
|
| 26 |
So by setting ACCEPT_KEYWORDS="~x86" on a amd64 profile you might install |
| 27 |
packages that are only tested for ~x86. This can lead to serious problems |
| 28 |
with packages that are broken on amd64 (and therefore not keyworded as amd64) |
| 29 |
|
| 30 |
You should set ACCEPT_KEYWORDS to the correct value for your profile. |
| 31 |
Then run the following to make sure all installed packages are keyworded for |
| 32 |
your profile. |
| 33 |
|
| 34 |
# emerge -DNup world |
| 35 |
# revdep-rebuild -p |
| 36 |
-- |
| 37 |
gentoo-amd64@g.o mailing list |
Archives