From: "Théo Tyburn" <theo.tyburn@posteo.net>
To: Richard Sent <richard@freakingpenguin.com>
Cc: Tomas Volf <wolf@wolfsden.cz>, help-guix@gnu.org
Subject: Re: Make a simple guile script to a package - source local file
Date: Sat, 20 Jan 2024 12:32:08 +0000 [thread overview]
Message-ID: <87frysi3fz.fsf@posteo.net> (raw)
In-Reply-To: <877ck5djur.fsf@freakingpenguin.com>
Richard Sent <richard@freakingpenguin.com> writes:
> Depending on what you mean by polluting or re-entering the profile
> information all the time this might not be what you want. When I write
> scripts that rely on specific dependencies I don't want to permanently
> install, I write the shebang like this:
>
> --8<---------------cut here---------------start------------->8---
> #!/usr/bin/env -S guix shell ruby ruby-colorize password-store -- ruby
> --8<---------------cut here---------------end--------------->8---
This is a really nice trick !
Unfortunately you either have to reevaluate the profile at each
run or create a profile and do something like
#!/usr/bin/env -S guix shell -p
${GUIX_EXTRA_PROFILES}/python-pydbus/python-pydbus -- python3
> This relies on /usr/bin/env supporting -S, which to my understanding
> isn't POSIX but instead a coreutils extension. Pretty sure --container
> would work here but I've not tried it.
Also as you mentioned, I fear I will not be able to directly
distribute this to people not running guix.
But thanks for the hint :)
next prev parent reply other threads:[~2024-01-20 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 18:01 Make a simple guile script to a package - source local file Théo Tyburn
2023-10-26 14:18 ` Tomas Volf
2023-10-29 8:44 ` Théo Tyburn
2024-01-19 21:28 ` Théo Tyburn
2024-01-19 21:46 ` Felix Lechner via
2024-01-20 17:19 ` Théo Tyburn
2024-01-19 22:44 ` Richard Sent
2024-01-20 12:32 ` Théo Tyburn [this message]
2024-01-20 13:29 ` Tomas Volf
2024-01-20 18:05 ` Théo Tyburn
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=87frysi3fz.fsf@posteo.net \
--to=theo.tyburn@posteo.net \
--cc=help-guix@gnu.org \
--cc=richard@freakingpenguin.com \
--cc=wolf@wolfsden.cz \
/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.