unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Howto run guix.el correctly?
Date: Mon, 01 Dec 2014 13:49:49 +0100	[thread overview]
Message-ID: <87fvczedqq.fsf@gnu.org> (raw)
In-Reply-To: <874mtf5zp4.fsf@gmail.com> (Alex Kost's message of "Mon, 01 Dec 2014 15:20:23 +0300")

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.

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’.

  reply	other threads:[~2014-12-01 12:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 22:28 Howto run guix.el correctly? 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2014-12-01 17:15 Federico Beffa
2014-12-02  7:52 ` 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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fvczedqq.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --cc=guix-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).