Hello, coreutils installs some of the utilities in /bin and create symbolic link in /usr/bin. sed installs itself in /bin but does not create symbolic link (although it looks like in x86 stage3 there is hand made one). eselect-vi use /usr/bin/sed explicitly. I believe the problem is in sed it should behave like coreutils, and create /usr/bin/sed symbolic link. Thanks!
anything relying on a hardcoded path is broken. fix the package in question.
There's nothing sed specific in vi.eselect. eselect itself determines the path to sed at configure time, but I don't see what should be wrong with this.
True. I see that latest vi.eselect was already fixed. It does not use sed or any hardcoded values anymore.