Alex Kost <[email protected]> skribis: > Ludovic Courtès (2014-11-27 01:41 +0300) wrote:
[...] >>> The problem is that I don't understand what these %standard-emacs-phases >>> should be, >> >> (define %standard-emacs-phases >> (alist-cons-after >> 'install 'post-install >> (lambda* (#:key outputs #:allow-other-keys) >> (install-autoloads (assoc-ref outputs "out"))) >> %standard-phases)) > > Sorry, I didn't get how it would work. I realized that I don't > understand how there could be a generalized ‘install-autoloads’ > procedure as it should do different things for different packages. Arf, yes, that’s a good point. Perhaps I just overlooked that. >>> that's why I wanted to do it step-by-step. I don't see general >>> patterns right now. Some packages would require just making a link as >>> with geiser, other packages require generating autoloads and maybe >>> some others require additional steps. What about making >>> "wip-emacs-packages" branch and to put the appropriate changes there >>> for now? >> >> Sure! > > Thanks, I have created "wip-emacs-packages" branch: the elisp code is > ready, so now I'm going to walk through existing emacs packages in order > to add “…-autoloads.el” to each one. I just browsed it, and it looks good so far. I was just thinking: if we want to take over the Emacs world, we need an ELPA importer for ‘guix import’. (In case you were wondering what to do next. ;-)) Thanks, Ludo’.
