| 1 |
On Tue, 8 Sep 2020 15:29:22 +0100, Wols Lists wrote: |
| 2 |
|
| 3 |
> > When I subsequently ran "emerge --depclean --ask" it wanted to unmerge |
| 4 |
> > dev-lang/rust-bin. |
| 5 |
> |
| 6 |
> rust-bin was emerged with the -1 option, ie "don't stick it in world" |
| 7 |
> option |
| 8 |
> > |
| 9 |
> > I had to manually unmerge dev-lang/rust to get rid of it (which then |
| 10 |
> > prevented --depclean from trying to unmerge rust-bin). |
| 11 |
> > |
| 12 |
> So --depclean, relying on what is in world, notices that nothing has a |
| 13 |
> dependency on rust-bin and wants to remove it. |
| 14 |
|
| 15 |
That's because rust was also installed, and only one of them is needed to |
| 16 |
satisfy the dependency of virtual/rust. |
| 17 |
|
| 18 |
> What you need to do (and this is a pain, but ...) is to add rust-bin to |
| 19 |
> the world file. There may be a --select option (opposite of deselect), |
| 20 |
> or I'd just manually add it to the world file. |
| 21 |
> |
| 22 |
> At which point, anything with the virtual rust dependency will notice |
| 23 |
> that rust-bin is installed, and use that. |
| 24 |
> |
| 25 |
> There's no way I know of to tell portage to use rust-bin rather than |
| 26 |
> rust to satisfy the virtual and, indeed, it makes sense for rust-bin |
| 27 |
> *not* to be the default. |
| 28 |
|
| 29 |
There is a way, uninstall rust. virtual/rust requires only one of rust |
| 30 |
and rust-bin, if both are installed it will take rust meaning rust-bin |
| 31 |
gets depcleaned. If only one is installed, the virtual will take that. If |
| 32 |
neither is install, the virtual will pull in rust. |
| 33 |
|
| 34 |
Adding packages like this to the world file is storing up problems for |
| 35 |
later. |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
Neil Bothwick |
| 40 |
|
| 41 |
Top Oxymorons Number 22: Childproof |
Archives