1 |
On Wednesday 18 January 2006 11:40, Michael Ulm wrote: |
2 |
> 1) spending several hours checking out the ~amd64 packages I |
3 |
> emerged, to see if they are available in stable, and which |
4 |
> dependencies can then be brought back to amd64. As spare |
5 |
> time is a rather scarce resource for me, I don't want to do |
6 |
> this unless absolutely necessary |
7 |
You could (re)move the package.keywords and see what packages get downgraded |
8 |
without ~amd64. That should give a good indication. |
9 |
|
10 |
> 2) Go totally ~amd64. I am slightly worried about system |
11 |
> stability in this scenario. Every time the system hiccups |
12 |
> my wife tells me that this never happened in Windows... |
13 |
~amd64 is ment for testing and as such beta software can and will be entered |
14 |
in the portage tree. It really depends on your problem solving skills and |
15 |
knowledge of portage. If you feel you can deal with this you could try it. |
16 |
|
17 |
I have more problems with windows then I do running ~amd64 by default. But I |
18 |
have to admit that I enjoy solving problems and trying new software so it's |
19 |
probably not a good comparison with your demands. |
20 |
|
21 |
With the current amount of changes to the portage and baselayout packages it's |
22 |
probably better to stick with amd64 and use packages.keywords if you don't |
23 |
want any trouble. |
24 |
|
25 |
There is however another option, help Gentoo ! |
26 |
If you've got a ~amd64 package running that's not available in amd64 and it's |
27 |
running stable. Let the devs know, write a bugreport, and let them move it to |
28 |
amd64. |
29 |
This will help the whole Gentoo community, isn't it great :) |
30 |
-- |
31 |
gentoo-amd64@g.o mailing list |