unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: tumashu <tumashu@163.com>
Cc: guix <guix-devel@gnu.org>
Subject: Re: emacs.scm: Suggest add emacs-next or emacs-snapshot
Date: Thu, 12 Nov 2015 13:52:47 +0100	[thread overview]
Message-ID: <87fv0bz8f4.fsf@gnu.org> (raw)
In-Reply-To: <11cf533a.13b0.150f91df556.Coremail.tumashu@163.com> (tumashu@163.com's message of "Thu, 12 Nov 2015 08:35:01 +0800 (CST)")

tumashu <tumashu@163.com> skribis:

> Suggest add emacs-next or emacs-snapshot and let guile-emacs inherit it, The reason is that
> user can use it build emacs from emacs.git conveniently, for example:
>
>     guix build emacs-snapshot --with-source=./emacs-snapshot-20151111.tar.gz

To use --with-source, all you need to do is to rename the tarball to
‘emacs-20151111.tar.gz’; after that, you can run:

  guix build emacs --with-source=emacs-20151111.tar.gz

That’s because --with-source expects the tarball name to match the
package name (info "(guix) Invoking guix build").

Now, it might make sense to also provide an ‘emacs-snapshot’ package,
built from a Git checkout and regularly updated.  Would you like to try
that?

I think the package would simply inherit from ‘guile-emacs’ and provide
a different ‘name’, ‘version’, and ‘source’.

Thanks,
Ludo’.

  reply	other threads:[~2015-11-12 12:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12  0:35 emacs.scm: Suggest add emacs-next or emacs-snapshot tumashu
2015-11-12 12:52 ` Ludovic Courtès [this message]
2015-11-13  0:26   ` tumashu
2015-11-13  8:04     ` Ricardo Wurmus
2015-11-13  8:47     ` Ludovic Courtès
2015-11-13 12:00       ` Feng Shu
2015-11-13 14:44         ` Ricardo Wurmus
2015-11-14 11:25           ` Ludovic Courtès
2015-11-13 11:56   ` Feng Shu
2015-11-14 11:32     ` Ludovic Courtès
2015-11-15  7:06       ` Feng Shu

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=87fv0bz8f4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=tumashu@163.com \
    /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).