| 1 |
On Mon, 2005-11-28 at 19:52 -0800, Mark Knecht wrote: |
| 2 |
|
| 3 |
> A questions though. Just because an app is not tested on AMD64, and |
| 4 |
> hence not keyworded with amd64 or ~amd64, doesn't mean it has a |
| 5 |
> problem, does it? It just means it's not tested, right? Or am I |
| 6 |
> incorrect in that? |
| 7 |
|
| 8 |
Sure, but you it depends if you want to make all x86 (but not amd64 or |
| 9 |
~amd64) apps available. My personal preference is to clone the ebuilds |
| 10 |
of stuff I want to try that hasn't got an amd keyword of one sort or |
| 11 |
another into my overlay directory and then build them. This means my |
| 12 |
systems is: |
| 13 |
|
| 14 |
* mainly stable amd64 packages |
| 15 |
* with a selection of ~amd64 packages (via package.keywords) |
| 16 |
* with a few cloned/overlayed x86 only builds manually editied to be |
| 17 |
~amd64 |
| 18 |
|
| 19 |
Hopefully this stops you whole system being pulled into an unstable |
| 20 |
state. |
| 21 |
|
| 22 |
-- |
| 23 |
Alex, homepage: http://www.bennee.com/~alex/ |
| 24 |
If I am elected, the concrete barriers around the WHITE HOUSE will be |
| 25 |
replaced by tasteful foam replicas of ANN MARGARET! |
| 26 |
|
| 27 |
-- |
| 28 |
gentoo-amd64@g.o mailing list |
Archives