1 |
> I wonder if it's worth the trouble. I read here that running a full ~x86 |
2 |
> system would probably be easier. And I'd like to try, but while going from |
3 |
> x86 to ~x86 is easy, the other way is quite hard, isn't it? If possible at |
4 |
> all. |
5 |
|
6 |
I just wanted to throw my two-cents in here, although much has been said. |
7 |
|
8 |
I was running ~x86 for about two years. Then I waited 6 months and |
9 |
was able to shift to x86 with only a few things in the keywords. (For |
10 |
example, I had already shifted to openrc and I didn't see the point in |
11 |
shifting back and then back-once-again.) However, for these cases, I |
12 |
almost exclusively keyword <= version numbers, so that, in theory, I |
13 |
will eventually hit x86 minus a very few packages (for example, the |
14 |
ones that there is no x86 version available). |
15 |
|
16 |
But honestly, I've been nearly stable (x86) for a couple months now, |
17 |
and I can't say that the system seems any different. Problems still |
18 |
crop up, and I still have to deal with them. |
19 |
|
20 |
As one poster mentioned, when I was running ~x86 and an ebuild was |
21 |
annoying, I'd just emerge the stable one. This was a solution for 90% |
22 |
of the things I couldn't google up a bug report on. But the problems |
23 |
I've hit lately are taking me a lot more time. It could be the mixing |
24 |
of x86 ~and x86, even though the mixture is nearly all x86. |
25 |
|
26 |
While shifitng from ~x86 to x86 is 'harder' than the other way around, |
27 |
basically the way you're shifting is, by-and-large, just waiting for |
28 |
x86 to catch up to ~x86. |
29 |
|
30 |
Regards, |
31 |
daid |