From: pinoaffe <pinoaffe@airmail.cc>
To: indieterminacy <indieterminacy@libre.brussels>
Cc: pinoaffe <pinoaffe@airmail.cc>, jgart <jgart@dismail.de>,
guix-devel@gnu.org
Subject: Re: Guix Goals: One Hackable Developer Tool To Rule Them All
Date: Thu, 13 Oct 2022 16:55:33 +0200 [thread overview]
Message-ID: <87zgdzpxzb.fsf@airmail.cc> (raw)
In-Reply-To: <b8465f9e1774827d018140b7b647aa97@libre.brussels>
indieterminacy <indieterminacy@libre.brussels> writes:
> Sorry if this comes off as facetious (because this is an interesting
> proposal) but hasnt Make cornered a lot of these usecases well enough?
It has covered some of these usecases to a certain degree, but in my
opinion there's a lot of room for improvement.
As an example, setting up make to run a particular command in a
particular environment (e.g., with certain packages available) is (imo)
quite annoying. It would be possible to shell out to guix from within a
makefile, but at that point, it's (imo) way cleaner if this can be
handled by guix.
Furthermore, doing this ckind of configuration in a makefile means that
the same or very similar make commands would need to be put in many
projects' makefiles, this could be implemented a lot cleaner within guix.
next prev parent reply other threads:[~2022-10-13 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 6:07 Guix Goals: One Hackable Developer Tool To Rule Them All jgart
2022-10-13 13:03 ` zimoun
2022-10-13 13:56 ` pinoaffe
2022-10-13 14:34 ` indieterminacy
2022-10-13 14:55 ` pinoaffe [this message]
2022-10-14 2:24 ` jgart
2022-10-16 13:11 ` Liliana Marie Prikler
2022-10-16 17:54 ` jgart
2022-10-16 18:41 ` jgart
2022-10-16 18:50 ` Liliana Marie Prikler
2022-10-16 20:03 ` jgart
2022-10-16 23:22 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2022-10-17 19:08 ` Liliana Marie Prikler
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=87zgdzpxzb.fsf@airmail.cc \
--to=pinoaffe@airmail.cc \
--cc=guix-devel@gnu.org \
--cc=indieterminacy@libre.brussels \
--cc=jgart@dismail.de \
/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.