1 |
Matt Harrison wrote: |
2 |
|
3 |
> The problem is that even though the selinux USE flag isn't exabled, packages |
4 |
> like coreutils are still linking into libselinux. So if I remove libselinux |
5 |
> and all the selinux related packages, it breaks a whole load of binaries on |
6 |
> the system, so much so that I can't recompile packages afterwards. |
7 |
|
8 |
Once you switch to a non-SELinux profile you still need to rebuild the |
9 |
packages that used the library. Building them without the selinux USE |
10 |
flag will prevent them from linking to the library. Once they're all |
11 |
rebuilt, then you can remove the SELinux userland stuff. |
12 |
|
13 |
To easily get this list of packages you have multiple options. The |
14 |
easiest way is to use revdep-rebuild with the --library option, but last |
15 |
time I checked revdep-rebuild crashed when you supplied a library. |
16 |
Alternately, you could run emerge with the --newuse flag, which will |
17 |
pick up any packages that used to have the selinux USE flag and now |
18 |
don't. Of course, if you want to be extra safe, just rebuild everything: |
19 |
|
20 |
emerge -e @world |