From: "Philip McGrath" <philip@philipmcgrath.com>
To: "Felix Lechner via" <help-guix@gnu.org>
Subject: Re: Using Makefile to run guix shell?
Date: Fri, 09 Dec 2022 13:38:04 -0500 [thread overview]
Message-ID: <b9653239-2866-4d51-9dee-9986bee69f03@app.fastmail.com> (raw)
In-Reply-To: <87zgbzdy4g.fsf@polidoro.io>
On Wed, Dec 7, 2022, at 10:26 AM, Peter Polidoro wrote:
>> And then all you need to do is run ``guix shell'', and it will
>> automatically
>> pick up that manifest or package file.
>
> That works well for just the "guix shell" command, but what if I
> want shortcuts to a whole set of commands?
>
> For example, I might want a command to automatically generate
> project metadata from an org file running "make metadata":
>
> metadata:
> $(GUIX-CONTAINER) -- sh -c "emacs --batch -Q -l .init.el --eval
> '(process-org \".metadata.org\")'"
>
> This seems to work well, but I just wondered if putting a Makefile
> into every project root may cause conflicts for some build
> systems.
>
> Is there something better to use than make for such command
> shortcuts?
The ability to to this sort of thing is one of the interesting aspects of Nix Flakes. See in particular the “apps” output attributes and the `nix run` command: https://nixos.wiki/wiki/Flakes
next prev parent reply other threads:[~2022-12-09 18:38 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
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 [this message]
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=b9653239-2866-4d51-9dee-9986bee69f03@app.fastmail.com \
--to=philip@philipmcgrath.com \
--cc=help-guix@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.
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).