| 1 |
On Tue, 2002-10-22 at 14:13, Louis-Philippe Brochu wrote: |
| 2 |
> This is great news because it happened a couple times that i emerged a |
| 3 |
> new ebuild that wasn't simply working (tightVNC and Postfix comes to |
| 4 |
> mind) so i had to revert to the previous version manually. Previously i |
| 5 |
> would never schedule an "emerge rsync && emerge world -u" because it |
| 6 |
> would often break existing packages and left my system not working properly. |
| 7 |
> |
| 8 |
> This new feature is really great, however it would be great to be able |
| 9 |
> to specify for which packages you want to enable this. You could be |
| 10 |
> using stable packages everywhere except for certain softwares which you |
| 11 |
> want the latest version and don't care for stability (web browsers or |
| 12 |
> games for example). |
| 13 |
|
| 14 |
This can be done very easily... if you don't want to run all the testing |
| 15 |
pkgs full time, but simply want one or two pkgs you can do it like this: |
| 16 |
|
| 17 |
ACCEPT_KEYWORDS="~x86" emerge somegame |
| 18 |
|
| 19 |
or alternatively, you can always install an ebuild by referencing the |
| 20 |
ebuild file directly (this supercedes keywords, etc) |
| 21 |
|
| 22 |
emerge /usr/portage/app-games/somegame/somegame-0.1.ebuild (or if it is |
| 23 |
in your current working dir, just emerge somegame-0.1.ebuild) |
| 24 |
|
| 25 |
You don't have to include the testing pkgs full time just to get a |
| 26 |
couple, there's almost always options if you look hard enough in linux |
| 27 |
:) |
| 28 |
|
| 29 |
Gerk |
Archives