unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Peter Polidoro <peter@polidoro.io>
To: help-guix@gnu.org
Subject: Using Makefile to run guix shell?
Date: Wed, 07 Dec 2022 09:47:16 -0500	[thread overview]
Message-ID: <874ju7fe2a.fsf@polidoro.io> (raw)

In the root of every project directory, I now include a 
channels.scm file and a manifest.scm file.

I was using direnv to automatically launch guix shell, but I 
wanted more flexibility to easily launch variations of guix shell.

Now I am also including a Makefile in the root of every project 
directory so I can use "make guix-shell" or "make guix-container" 
or "make project-documentation" etc to quickly run commands.

This works well for certain types of projects, but there could be 
conflicts with projects that expect or automatically generate 
their own Makefiles.

I could use a different Makefile name for my guix commands, but 
that makes my commands less convenient to type.

Is it considered bad practice to use make like this? Is there a 
better way to do something similar?


             reply	other threads:[~2022-12-07 15:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07 14:47 Peter Polidoro [this message]
2022-12-07 15:12 ` Using Makefile to run guix shell? (
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

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=874ju7fe2a.fsf@polidoro.io \
    --to=peter@polidoro.io \
    --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).