| 1 |
I manage one desktop and one server for my research group and |
| 2 |
stability is the must. So I'm amd64, but still some packages need to be |
| 3 |
~amd64. |
| 4 |
|
| 5 |
What I do is not to add the package to package.keywords file, rather |
| 6 |
use one shot ACCEPT_KEYWORDS='~amd64' emerge .... |
| 7 |
(I know, this is not a recommended procedure) |
| 8 |
|
| 9 |
This way, emerge -UD wants to downgrade these packages to stable. |
| 10 |
Since I never blindly upgrade, it is not a problem for me. |
| 11 |
Now emerge -pvuD shows me what packages are ~amd64 and what is the |
| 12 |
latest stable issue. |
| 13 |
|
| 14 |
This way, of course, you will not get unstable package |
| 15 |
upgraded when even newer ~amd64 version comes out. |
| 16 |
However this is suits me as well - I'm not after the newest possible package if |
| 17 |
the current unstable works, and if it has problems, I'll be investigating it |
| 18 |
anyway. |
| 19 |
|
| 20 |
As people mentioned, adding '=' sign in front of the package names |
| 21 |
in package.keywords achieves the same, in, perhaps, cleaner way. |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Dmitri Pogosyan Department of Physics |
| 26 |
Associate Professor University of Alberta |
| 27 |
tel 1-780-492-2150 412 Avadh Bhatia Physics Labs |
| 28 |
fax 1-780-492-0714 Edmonton, AB, T6G 2J1, CANADA |
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
gentoo-amd64@g.o mailing list |
Archives