From /usr/portage/app-emacs/erc/erc-5.0.2.ebuild:
elisp-site-file-install ${FILESDIR}/${PV}/50erc-gentoo.el
But see the entry of `50erc-gentoo.el' in app-emacs/erc/Manifest:
MD5 525caef1ddd566109a224e44097d6e73 files/50erc-gentoo.el 101
I.e. `50erc-gentoo.el' is installed directly into `${FILESDIR}' and not
into `${FILESDIR}/5.0.2' where the ebuild above assumes it to be. That's
why this file is not installed into `/usr/share/emacs/site-lisp'[*],
from there not generated into `site-gentoo.el' and thus is not automatically
loaded upon emacs' start up.
Solution deems rather straightforward.
[*] I wonder why `emerge' doesn't barf upon the failure of `cp' internally to
`elisp-site-file-install'. Isn't there something like a `set -e' anywhere
in the build process?
Reproducible: Always
Steps to Reproduce:
1. emerge --unmerge app-emacs/erc
2. emerge =app-emacs/erc-5.0.2
3.
Actual Results:
$ ls /usr/share/emacs/site-lisp/50erc-gentoo.el
ls: /usr/share/emacs/site-lisp/50erc-gentoo.el: No such file or directory
Expected Results:
ls /usr/share/emacs/site-lisp/50erc-gentoo.el
/usr/share/emacs/site-lisp/50erc-gentoo.el
