From: Federico Beffa <beffa@ieee.org>
To: ludo@gnu.org, Guix-devel <guix-devel@gnu.org>,
Alex Kost <alezost@gmail.com>
Subject: Re: Howto run guix.el correctly?
Date: Mon, 1 Dec 2014 18:15:07 +0100 [thread overview]
Message-ID: <CAKrPhPOZ2BvfYDJOSLc=ji1A2nRcrTxNASGFRnKwEdHDG7cuSQ@mail.gmail.com> (raw)
ludo@gnu.org (Ludovic Courtès) writes:
> Alex Kost <alezost@gmail.com> 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.
>
AFAIU the initialization of each package is already defined inside each
package by the author. The way emacs's packaging infrastructure works
goes along the lines (see (elisp) Packaging Basics):
* At installation:
- Search every Lisp file in the content directory for autoload magic
comments (*note Autoload::). These autoload definitions are saved
to a file named `NAME-autoloads.el' in the package's content
directory.
- Byte-compiles every Lisp file in the package.
- Add the package's content directory to `load-path', and evaluates
the autoload definitions in `NAME-autoloads.el'.
* At startup:
- Emacs scans for a predefined directory for NAME-autoloads.el files
and evaluates them ('package-initialize' function). We could maybe
exploit 'after-init-hook' or something something similar.
Regards,
Fede
next reply other threads:[~2014-12-01 17:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 17:15 Federico Beffa [this message]
2014-12-02 7:52 ` Howto run guix.el correctly? Alex Kost
-- strict thread matches above, loose matches on Subject: below --
2014-11-21 22:28 Adam Pribyl
2014-11-22 8:03 ` Alex Kost
2014-11-22 10:52 ` Ludovic Courtès
2014-11-22 12:04 ` Alex Kost
2014-11-22 18:49 ` Alex Kost
2014-11-22 21:04 ` Adam Pribyl
2014-11-22 21:11 ` David Thompson
2014-11-22 22:17 ` Ludovic Courtès
2014-11-23 7:01 ` Alex Kost
2014-11-24 20:42 ` Ludovic Courtès
2014-11-25 13:58 ` Alex Kost
2014-11-26 16:23 ` Ludovic Courtès
2014-11-26 20:38 ` Alex Kost
2014-11-26 22:41 ` Ludovic Courtès
2014-12-01 12:20 ` Alex Kost
2014-12-01 12:49 ` Ludovic Courtès
2014-12-02 7:46 ` Alex Kost
2014-12-02 8:39 ` Ludovic Courtès
2014-12-02 19:13 ` Alex Kost
2014-11-26 20:14 ` Alex Kost
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKrPhPOZ2BvfYDJOSLc=ji1A2nRcrTxNASGFRnKwEdHDG7cuSQ@mail.gmail.com' \
--to=beffa@ieee.org \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.