1 |
On Wed, Jan 7, 2015 at 8:06 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
2 |
> |
3 |
> openrc should be seamless. I forget the exact timelines, but IIRC you |
4 |
> will also hit baselayout-2 migration. That one was very smooth and well |
5 |
> documented so you shouldn't have much trouble. |
6 |
> |
7 |
|
8 |
If it is already running openrc then he is past that migration. |
9 |
|
10 |
If it isn't, then it isn't exactly seamless. You might want to give |
11 |
thought in that case to whether long-term you want to be on openrc or |
12 |
systemd. It is probably as much work to migrate to either. However, |
13 |
I suspect that you're already on openrc in which case I wouldn't try |
14 |
to throw a change like that into the mix - you'll be lucky enough to |
15 |
get the thing to boot keeping things the same. |
16 |
|
17 |
I didn't see this suggestion yet. Build binary packages of everything |
18 |
from a new install, and update using those. Updating using a binary |
19 |
package is far more likely to work. |
20 |
|
21 |
Just create a stage3 chroot, set your use flags the way you want them, |
22 |
do an emerge -e @system with buildpkg turned on inside, then migrate |
23 |
those packages to your host and after a backup do an emerge -uk |
24 |
@system. Once you get the system set updated most of the rest should |
25 |
go fairly smoothly, but you could extend this to other packages. |
26 |
|
27 |
You don't necessarily need to do the first pass update with your final |
28 |
use flags either - you could just install binary packages with generic |
29 |
use flags and then just do an emerge -uN world to rebuild everything |
30 |
now that you're past the hump. |
31 |
|
32 |
-- |
33 |
Rich |