From: Peter Polidoro <peter@polidoro.io>
To: "(" <paren@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Using Makefile to run guix shell?
Date: Wed, 07 Dec 2022 13:27:30 -0500 [thread overview]
Message-ID: <87edtbdpmo.fsf@polidoro.io> (raw)
In-Reply-To: <COVP4XE0TKC7.3188L000MYXUY@guix-framework>
> Why not just do:
>
> guix shell -- make metadata
I do like the idea of not making it depend on guix.
One of the things I am trying to avoid, though, is typing long
guix commands.
When I type "make guix-shell", what I really want is something
like:
guix-shell:
guix time-machine -C channels.scm -- shell --pure --check -m
manifest.scm
Or if I am doing embedded work I might want type "make
serial-shell" to do something like:
serial-shell:
guix time-machine -C channels.scm -- shell -m manifest.scm
--container --expose=$(PORT) picocom -- picocom -b 9600 -f n -y
n -d 8 -p 1 -c $(PORT)
I guess I am just curious how other people manage such long
commands?
next prev parent reply other threads:[~2022-12-07 18:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 14:47 Using Makefile to run guix shell? Peter Polidoro
2022-12-07 15:12 ` (
2022-12-07 15:26 ` Peter Polidoro
2022-12-07 15:38 ` (
2022-12-07 18:27 ` Peter Polidoro [this message]
2022-12-07 21:01 ` Wojtek Kosior via
2022-12-08 10:44 ` zimoun
2022-12-08 14:21 ` Peter Polidoro
2022-12-08 15:30 ` Wojtek Kosior via
2022-12-08 18:47 ` zimoun
2022-12-08 21:30 ` Wojtek Kosior via
2022-12-08 23:04 ` zimoun
2022-12-08 23:24 ` Wojtek Kosior via
2022-12-09 17:46 ` Peter Polidoro
2022-12-10 13:21 ` zimoun
2022-12-12 17:55 ` Peter Polidoro
2022-12-12 19:00 ` Wojtek Kosior via
2022-12-09 18:38 ` Philip McGrath
2022-12-07 17:08 ` Wolf
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=87edtbdpmo.fsf@polidoro.io \
--to=peter@polidoro.io \
--cc=help-guix@gnu.org \
--cc=paren@disroot.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.
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).