From: Wojtek Kosior via <help-guix@gnu.org>
To: Peter Polidoro <peter@polidoro.io>
Cc: "(" <paren@disroot.org>, help-guix@gnu.org
Subject: Re: Using Makefile to run guix shell?
Date: Wed, 7 Dec 2022 22:01:21 +0100 [thread overview]
Message-ID: <20221207220121.6699388d.koszko@koszko.org> (raw)
In-Reply-To: <87edtbdpmo.fsf@polidoro.io>
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
> > 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?
>
I recently came up with the same solution as you[1][2] :)
I haven't considered hard requirement on Guix a major issue. But I did
for a moment think about another solution to the same problem. I
believe it'd be possible to use a mere shell script instead of
a Makefile. Or a mere guile script or Python script (setup.py on
steroids?) :)
Wojtek
[1] https://git.koszko.org/pydrilla/
[2] https://git.koszko.org/koszko-org-server/
-- (sig_start)
website: https://koszko.org/koszko.html
PGP: https://koszko.org/key.gpg
fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79 FD1A
Meet Kraków saints! #21: saint Kazimierz
Poznaj świętych krakowskich! #21: święty Kazimierz
https://pl.wikipedia.org/wiki/Święty_Kazimierz
-- (sig_end)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-12-07 21:02 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
2022-12-07 21:01 ` Wojtek Kosior via [this message]
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=20221207220121.6699388d.koszko@koszko.org \
--to=help-guix@gnu.org \
--cc=koszko@koszko.org \
--cc=paren@disroot.org \
--cc=peter@polidoro.io \
/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).