all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Feng Shu <tumashu@163.com>
Cc: guix-devel@gnu.org
Subject: Re: emacs.scm: Suggest add emacs-next or emacs-snapshot
Date: Fri, 13 Nov 2015 15:44:20 +0100	[thread overview]
Message-ID: <idjegfuc62j.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <876116hzy7.fsf@163.com>


Feng Shu <tumashu@163.com> writes:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Currently you have to do:
>>
>>   guix package -i $(guix build emacs --with-source=…/emacs-20151111.tar.gz)
>>
>> Not as convenient as one would like.  I guess we could add --with-source
>> directly in ‘guix package’.
>
> I agree and suggest add a way which can override name and verison, for
> example:
>
>   guix package -i emacs-snapshot --with-source=/path/to/emacs.git --override-name=emacs-snapshot --override-version=20151111

I don’t like to add override-name and override-version flags.  They
don’t seem very useful.  After all, every different build gets its own
directory in the store, so “override-version” seems to be useless.

“override-name” just duplicates the package name, so I fail to see how
it would be an improvement.

I do agree that it would be a little nicer if we could build and install
a package from a directory, rather than just from a tarball.

~~ Ricardo

  reply	other threads:[~2015-11-13 14:44 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=idjegfuc62j.fsf@bimsb-sys02.mdc-berlin.net \
    --to=ricardo.wurmus@mdc-berlin.de \
    --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 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.