From: Mekeor Melire <mekeor.melire@gmail.com>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: Git-style aliases in Guix?
Date: Mon, 27 Feb 2017 20:01:56 +0100 [thread overview]
Message-ID: <87o9xna257.fsf@gmail.com> (raw)
In-Reply-To: <20170227151517.GA9476@jocasta.intra>
John Darrington <john@darrington.wattle.id.au> writes:
> On Mon, Feb 27, 2017 at 09:30:07AM +0100, Mekeor Melire wrote:
>
> John Darrington <john@darrington.wattle.id.au> writes:
>
> > On Sun, Feb 26, 2017 at 10:15:10PM +0100, Mekeor Melire wrote:
> >
> > Concerning how to implement this alias feature within Guix, I'd first
> > like to pose a much broader question. So, on GuixSD you have a
> > configuration, written in Scheme, for your operating system. Couldn't we
> > make Guix have a scheme-configuration file for itself, as well?
> >
> > We do. guix/config.scm
>
> How can you configure Guix itself in your config.scm? I'm only aware of
> the operating-system declaration which is used to configure the OS, not
> Guix itself.
>
> What kind of configuration had you in mind?
So, `operating-system` let's you declare an operating system. What if
there was a Scheme function called `guix` or so which allowed you to
configure Guix itself?
Then, defining Guix aliases could look as follows; maybe saved in a file
called guix.scm:
(guix
(aliases '(
("p" . "package")
("s" . "package -s")
("m" . "package -m"))))
And similar to `operating-system`, there would be many other
configuration fields...
next prev parent reply other threads:[~2017-02-27 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 20:59 Git-style aliases in Guix? Alex Griffin
2017-02-26 21:15 ` Mekeor Melire
2017-02-27 5:54 ` John Darrington
2017-02-27 8:30 ` Mekeor Melire
2017-02-27 15:15 ` John Darrington
2017-02-27 19:01 ` Mekeor Melire [this message]
2017-03-08 8:53 ` Ludovic Courtès
2017-03-09 3:27 ` Mekeor Melire
2017-03-09 10:53 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2017-02-25 20:58 Alex Griffin
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=87o9xna257.fsf@gmail.com \
--to=mekeor.melire@gmail.com \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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.