root@moon_gen_2:~# which esd /usr/bin/esd root@moon_gen_2:~# equery b /usr/bin/esd [ Searching for file(s) /usr/bin/esd in *... ] root@moon_gen_2:~# ls -l /usr/bin/esd lrwxrwxrwx 1 root root 20 2007-02-09 11:26 /usr/bin/esd -> //usr/bin/esound-esd root@moon_gen_2:~# equery b /usr/bin/esound-esd [ Searching for file(s) /usr/bin/esound-esd in *... ] media-sound/esound-0.2.37-r1 (/usr/bin/esound-esd) root@moon_gen_2:~# I expected /usr/bin/esd to something; from memory, even symlinks should belong to some package ... and in our case, I expect esd to belong to esound-esd; who else could have create it ?
Created attachment 114610 [details] /tmp/emerge--info
Created attachment 114612 [details] media-sound:esound-0.2.37-r1 compile log
/usr/bin/esd symlink is chosen between esound-esd or pulseaudio's esdcompat script by the esd module for eselect (app-admin/eselect-esd).
NOTABUG.
then why not belong to app-admin/eselect-esd ?
(In reply to comment #5) > then why not belong to app-admin/eselect-esd ? Uh? How could it belong to anything? It's generated when you run eselect, not when you install something. CLOSED.