SOLVED: dev-dotnet/dotnet-sdk pulled in unexpectedly

[bent]

I'm doing a an `emerge -uavUD @world, and I noticed dotnet-sdk (which I'd previously installed) was in the list.

I don't want to wait for it to build this time, so I removed dotnet-sdk, and installed dotnet-sdk-bin (and virtual/dotnet-sdk)

I went back to resume the @world update, but portage still wants to build dotnet-sdk. I tried using `equery d`, and `emerge -t` to figure out what is still trying to bring it in, but there were no clues there. `emerge -t` showed `dotnet-sdk` at the top of the tree (with "N" for new), so I'm at a loss for why it's being rebuilt. I'm letting it do it anyway, but what am I missing here?
_________________
Back on the G after 15 years on the Cupertino Kool-aid

[logrusx]

[bent]

sorry, to clarify: I did not use the `--resume` flag, I simply re-ran the emerge command.
_________________
Back on the G after 15 years on the Cupertino Kool-aid

[GDH-gentoo]

[bent]

[bent]

Oh, my heavens. This is embarrassing. I'd checked that dev-dotnet/dotnet-sdk is not in my *world* file, but had not realised it was recorded in one of my *sets*, instead of virtual/dotnet-sdk like it should have been.

Case closed, thank you all for your help.

edit: I should probably put dotnet-sdk-bin in the set instead of the virtual, right?
_________________
Back on the G after 15 years on the Cupertino Kool-aid

[Hu]

If your preference is to always use the -bin when viable, and never let it build if not needed, then yes, I think you should put the -bin in the set.

[logrusx]

Once satisfied, things should not change unless you explicitly change them. Or cause a situation that changes them, which I can't think of what it may be right now.

Best Regards,
Georgi

[bent]