From: ludo@gnu.org (Ludovic Courtès)
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] build: emacs: Handle sources that are a single elisp file.
Date: Sat, 28 May 2016 17:36:04 +0200 [thread overview]
Message-ID: <87lh2ujiu3.fsf@gnu.org> (raw)
In-Reply-To: <1464358215-4416-1-git-send-email-dthompson2@worcester.edu> (David Thompson's message of "Fri, 27 May 2016 10:10:14 -0400")
David Thompson <dthompson2@worcester.edu> skribis:
> * guix/build/emacs-build-system.scm (gnu:unpack)
> (store-file->elisp-source-file, unpack): New procedures.
> (%standard-phases): Use the new unpack procedure.
Good idea, LGTM!
Could you adjust users of ‘uncompressed-file-fetch’ in a subsequent
commit, and remove ‘uncompressed-file-fetch’?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-05-28 15:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 14:10 [PATCH 1/2] build: emacs: Handle sources that are a single elisp file David Thompson
2016-05-27 14:10 ` [PATCH 2/2] gnu: Add emacs-better-defaults David Thompson
2016-05-28 14:05 ` Alex Kost
2016-05-28 15:37 ` Ludovic Courtès
2016-05-30 15:11 ` Thompson, David
2016-05-31 16:59 ` Mark H Weaver
2016-05-31 17:16 ` Thompson, David
2016-06-01 2:07 ` Mark H Weaver
2016-05-31 20:53 ` Alex Kost
2016-05-31 20:55 ` Thompson, David
2016-05-28 13:59 ` [PATCH 1/2] build: emacs: Handle sources that are a single elisp file Alex Kost
2016-05-28 15:36 ` Ludovic Courtès [this message]
2016-05-28 19:05 ` Alex Kost
2016-05-29 21:50 ` Ludovic Courtès
2016-05-30 10:14 ` Alex Kost
2016-05-30 11:55 ` Catonano
2016-05-30 12:42 ` Catonano
2016-05-30 15:12 ` Thompson, David
2016-05-30 16:27 ` Solving the ‘package-name->name+version’ name conflict. (was: [PATCH 1/2] build: emacs: Handle sources that are a single elisp file.) Mathieu Lirzin
2016-06-08 12:44 ` Solving the ‘package-name->name+version’ name conflict Ludovic Courtès
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=87lh2ujiu3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dthompson2@worcester.edu \
--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).