From: Wolf <wolf@wolfsden.cz>
To: Peter Polidoro <peter@polidoro.io>
Cc: help-guix@gnu.org
Subject: Re: Using Makefile to run guix shell?
Date: Wed, 7 Dec 2022 18:08:53 +0100 [thread overview]
Message-ID: <Y5DIpewOBJAMA31e@ws> (raw)
In-Reply-To: <874ju7fe2a.fsf@polidoro.io>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
On 2022-12-07 09:47:16 -0500, Peter Polidoro wrote:
> I could use a different Makefile name for my guix commands, but that makes
> my commands less convenient to type.
I guess you could do something like
alias ,make=make\ -f\ Makefile.mine
and then invoke it as
,make guix-shell
That will rid you of the risk of collision (especially if you pick
something more unique then Makefile.mine) while keeping it easy to
write.
But the alternative suggestion in this thread to do
guix shell -- make metadata
seems like a better approach, since it does not make guix a required
component to build your project.
W.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-12-08 16:22 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
2022-12-07 17:08 ` Wolf [this message]
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=Y5DIpewOBJAMA31e@ws \
--to=wolf@wolfsden.cz \
--cc=help-guix@gnu.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).