From: Amirouche Boubekki <amirouche@hypermove.net>
To: ludo@gnu.org
Cc: guix-devel@gnu.org, guix-devel-bounces+amirouche=hypermove.net@gnu.org
Subject: Re: guix edit
Date: Tue, 16 Jun 2015 23:28:08 +0200 [thread overview]
Message-ID: <12c45c67ba52d467419fefafc7120678@hypermove.net> (raw)
In-Reply-To: <87381rz9fa.fsf@gnu.org>
On 2015-06-16 22:26, ludo@gnu.org wrote:
> While looking at another package manager for ideas to steal, I found
> this one to be a good candidate:
>
> guix edit gcc-4.8
>
> will open $EDITOR (aka. “emacsclient”) on the definition of that
> package. This is pretty handy for developers (even when otherwise
> using
> Geiser, I think.)
>
> For “regular users,” it’s less useful because most of the time it will
> open an immutable file.
It's nice, even in read-only mode, to explore how guix is made.
> However, I envision a --clone option that would
> create a file with a module declaration and a template like:
>
> (define my-gcc
> (package (inherit gcc)
> ;; Complete here...
> )
>
> (This part is left as an exercise to the reader.)
>
> WDYT?
A usecase, I have in mind from experience, is being in vm/container and
having to edit the recipe for that specific vm *but* that recipe is in
the main normal repository. Like for instance, gcc for a specific
target. `guix edit gcc:4.5' should open or clone the correct recipe.
>
> Thanks,
> Ludo’.
--
Amirouche ~ amz3 ~ http://www.hyperdev.fr
next prev parent reply other threads:[~2015-06-16 21:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 20:26 guix edit Ludovic Courtès
2015-06-16 20:47 ` Thompson, David
2015-06-16 21:28 ` Amirouche Boubekki [this message]
2015-06-17 19:15 ` Ludovic Courtès
2015-06-18 10:55 ` Amirouche Boubekki
2015-06-16 23:29 ` Claes Wallin (韋嘉誠)
2015-06-17 19:16 ` Ludovic Courtès
2015-06-17 0:55 ` Eric Bavier
2015-06-17 19:20 ` Ludovic Courtès
2015-06-18 7:09 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12c45c67ba52d467419fefafc7120678@hypermove.net \
--to=amirouche@hypermove.net \
--cc=guix-devel-bounces+amirouche=hypermove.net@gnu.org \
--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.