| 1 |
Hello, |
| 2 |
|
| 3 |
On Tue, December 2, 2008 01:30, Mark Knecht wrote: |
| 4 |
> 1) Can I safely do an eselect profile set to one of the 2008.0 |
| 5 |
> profiles and then an emerge -pvDuN world to get an idea how much gets |
| 6 |
> rebuilt, but still be able to switch it back to the current profile? |
| 7 |
> (I.e. - just look at the tasks?) |
| 8 |
|
| 9 |
Sure. There shouldn't be any problem with that. The profile is just a |
| 10 |
symlink. |
| 11 |
|
| 12 |
On Tue, December 2, 2008 01:30, Mark Knecht wrote: |
| 13 |
> 2) What is the no-multilib profile. Is that no support for 32-bit. I |
| 14 |
> presume that builds libraries and support stuff faster over time? Does |
| 15 |
> it change applications much? |
| 16 |
|
| 17 |
The no-multilib profile avoids the building of any 32 bits stuff. This |
| 18 |
means that gcc and |
| 19 |
glibc will be built faster because you don't need to build the x68 |
| 20 |
compiler nor the 32 bits |
| 21 |
c libs. It also means that you will not be able to compile nor use 32 bits |
| 22 |
applications. |
| 23 |
|
| 24 |
There's no easy (nor supported) way to go back to multilib once you are in |
| 25 |
multilib, because |
| 26 |
that would involve producing a 32 bits gcc, which can't be done unless |
| 27 |
it's done via cross |
| 28 |
compiling. So, you will have to reinstall to get multilib working again. |
| 29 |
|
| 30 |
So, make really sure that you are not using 32 bits apps (flash and wine |
| 31 |
comes to my mind). |
| 32 |
|
| 33 |
> 3) What other questions should I be asking? (Like, since it's almost |
| 34 |
> 2009, when is 2009.0 coming and maybe I should wait?) ;-) |
| 35 |
|
| 36 |
I suggest to upgrade one step at a time. You are less likely to encounter |
| 37 |
problems. |
| 38 |
|
| 39 |
-- |
| 40 |
Jesús Guerrero |
Archives