| 1 |
> The scenario Meir mentions is basically the lazy-man's way out of |
| 2 |
> updating and maintaining a useful portage for the Gentoo/amd64 community. |
| 3 |
|
| 4 |
well, if i use ~amd64 i get the ebuilds that are to new, if i use amd64 |
| 5 |
only, i get ebuilds that are very old. gnome-2.4.2 for example is still |
| 6 |
masked for amd64 - i don't think that there were much changes from |
| 7 |
gnome-2.4.0 (which is marked as stable for amd64) to gnome-2.4.2 that |
| 8 |
prevent it compiling on amd64. |
| 9 |
|
| 10 |
the best way to overcome that dilemma is to use ACCEPT_KEYWORDS="amd64 |
| 11 |
x86". Using ACCEPT_KEYWORDS="amd64 ~amd64" would also give me gnome-2.6 |
| 12 |
for exmaple, but i don't want that, since the ebuilds are not ready yet, |
| 13 |
and it seems to be a common practice to modify ebuilds without changing |
| 14 |
the "-rX" part of the ebuilds version, and portage doesn't check if a |
| 15 |
ebuild has been modified. |
| 16 |
|
| 17 |
|
| 18 |
-- |
| 19 |
gentoo-dev@g.o mailing list |
Archives