| 1 |
On Sunday, April 10, 2016 08:09:28 AM Mick wrote: |
| 2 |
> On Saturday 09 Apr 2016 23:08:13 Neil Bothwick wrote: |
| 3 |
> > On Sat, 09 Apr 2016 22:41:01 +0100, Mick wrote: |
| 4 |
> > > > I'd use the KDE profile. The packages you install are still the ones |
| 5 |
> > > > you want but the profile means the USE flags are already as you need, |
| 6 |
> > > > and you can always tweak any you want different anyway. |
| 7 |
> > > |
| 8 |
> > > Reading eselect news I thought that the KDE profile and kde USE flag is |
| 9 |
> > > due to be withdrawn with Plasma 5 going stable, did I get this wrong? |
| 10 |
> > |
| 11 |
> > Sorry, I meant the plasma profile. |
| 12 |
> |
| 13 |
> I just noticed, one box is set at: |
| 14 |
> |
| 15 |
> [11] default/linux/amd64/13.0/no-multilib * |
| 16 |
> |
| 17 |
> Is this a reinstall exercise? |
| 18 |
|
| 19 |
Usually yes, but there is a work-around: |
| 20 |
|
| 21 |
Create a temporary chroot with a non-no-multilib installation. |
| 22 |
Use that to create binary packages. |
| 23 |
Then change the profile of the main installation to a non-no-multilib profile |
| 24 |
Using the packages created in the chroot, do an "emerge -e @world" |
| 25 |
|
| 26 |
That worked for me. (Found this in a blogposting somewhere) |
| 27 |
|
| 28 |
-- |
| 29 |
Joost |
Archives