Hi I am using sepia repl for perl+emacs ( http://search.cpan.org/~seano/Sepia-0.991_05/ ). Just in case someone is interested in ebuilds for Gentoo. Here they are.
Created attachment 274721 [details] latest stable release
Created attachment 274723 [details] git-build ebuild
Created attachment 274725 [details] emacs site file Put it in files sub-firectory
I just thought that maybe this ebuild should be called app-emacs/sepia instead of dev-perl/sepia :). I guest it is related more to emacs than perl. Please decide
Some comments: - Use the standard header from /usr/portage/header.txt please. - The ebuild depends on emacs-w3m-9999 which is not in the tree. - Probably better to inherit elisp.eclass instead of elisp-common.eclass. - In src_install: cd "${S}" shouldn't be necessary. S should be the working directory already. - The "for" loop is not needed, elisp-compile can take several arguments. for f in ./*.el; do elisp-compile "$f" || die done Besides, this belongs in src_compile (just use the default elisp_src_compile). - Ditto: for f in ./*.{el,elc}; do elisp-install "${PN}" "$f" || die done - elisp-site-regen should be called in pkg_post{inst,rm}. Again, the eclass default functions could be used here. (In reply to comment #4) > I just thought that maybe this ebuild should be called app-emacs/sepia > instead of dev-perl/sepia :). I guest it is related more to emacs than perl. > Please decide If we follow our other examples (e.g., app-emacs/pymacs and app-emacs/slime) then it should be in app-emacs indeed.
Is anyone still interested in this? If yes, please say so here and now!
Same here :) I guess my ebuild should be clean up and free to go.