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: Thu, 18 Jun 2015 12:55:13 +0200 [thread overview]
Message-ID: <4b93a73aab7bbc67c457dfa969a06b31@hypermove.net> (raw)
In-Reply-To: <87vbemxi20.fsf@gnu.org>
On 2015-06-17 21:15, ludo@gnu.org wrote:
> Amirouche Boubekki <amirouche@hypermove.net> skribis:
>
>> 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.
>
> Yes, ‘guix edit gcc-4.7’ edits the recipe for GCC 4.7.4.
I'm not sure this is real usecase for guix or maybe it's not required at
all and was specific to the way we were working in my company. I think
it's not supported right now in guix, but in Gentoo it does. You can
have serveral repositories and some repositories specific to one target.
GCC 4.7 can be overriden in the target specific repository. The reason
this is helpful, is that when we put a software version in stable -
ready to be built, we are sure it has no impact on other targets.
Right now it can of work with the env variable that guix package use to
look for packages.
Regards
next prev parent reply other threads:[~2015-06-18 10:55 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
2015-06-17 19:15 ` Ludovic Courtès
2015-06-18 10:55 ` Amirouche Boubekki [this message]
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=4b93a73aab7bbc67c457dfa969a06b31@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.