| 1 |
On Fri, Apr 27, 2018 at 2:18 PM Zac Medico <zmedico@g.o> wrote: |
| 2 |
|
| 3 |
> Actually, if things like sys-apps/s6 or sys-process/runit remain as |
| 4 |
> choices for virtual/init, this isn't going to solve the problem of |
| 5 |
> sys-apps/sysvinit being removed by emerge --depclean. In fact, if |
| 6 |
> virtual/init is not in the system set, then emerge --depclean will not |
| 7 |
> even warn about removing a system package when it removes |
| 8 |
sys-apps/sysvinit. |
| 9 |
|
| 10 |
Well, at least we don't have to worry about users accidentally uninstalling |
| 11 |
openssh, nano, or e2fsprogs (too bad if they use any other filesystem |
| 12 |
though). :) |
| 13 |
|
| 14 |
In general we don't have a great way of telling portage what we're actually |
| 15 |
using when various packages do more than one thing. If you have busybox |
| 16 |
installed you could conceivably remove a lot of other packages, but most |
| 17 |
users don't actually intend for this to happen. |
| 18 |
|
| 19 |
A USE flag that just pulls in a dep seems like the least evil solution |
| 20 |
unless somebody wants to come up with a more general one. |
| 21 |
|
| 22 |
-- |
| 23 |
Rich |
Archives