unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "(" <paren@disroot.org>
To: "Peter Polidoro" <peter@polidoro.io>, <help-guix@gnu.org>
Subject: Re: Using Makefile to run guix shell?
Date: Wed, 07 Dec 2022 15:12:30 +0000	[thread overview]
Message-ID: <COVOKVQPS0WH.2AX2TEHPYVN9A@guix-framework> (raw)
In-Reply-To: <874ju7fe2a.fsf@polidoro.io>

[-- Attachment #1: Type: text/plain, Size: 527 bytes --]

Heya,

On Wed Dec 7, 2022 at 2:47 PM GMT, Peter Polidoro wrote:
> Is it considered bad practice to use make like this? Is there a 
> better way to do something similar?

All you need to do is have a ``guix.scm'' or ``manifest.scm'' in your project
directory, then add it to the ``guix shell'' authorised directories:

  echo $PROJECT_DIR >> ~/.config/guix/shell-authorized-directories

And then all you need to do is run ``guix shell'', and it will automatically
pick up that manifest or package file.

    -- (

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2022-12-07 15:13 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 ` ( [this message]
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=COVOKVQPS0WH.2AX2TEHPYVN9A@guix-framework \
    --to=paren@disroot.org \
    --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).