From: Tomas Volf <wolf@wolfsden.cz>
To: "Théo Tyburn" <theo.tyburn@posteo.net>
Cc: help-guix@gnu.org
Subject: Re: Make a simple guile script to a package - source local file
Date: Thu, 26 Oct 2023 16:18:54 +0200 [thread overview]
Message-ID: <ZTp1TiDyDniEI_bW@ws> (raw)
In-Reply-To: <87jzrdtao6.fsf@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
On 2023-10-23 18:01:12 +0000, Théo Tyburn wrote:
> Hi,
>
> I have some guile CLI scripts and I would like to make them accessible
> in $PATH by putting each of them in a package.
>
> Is there a simple way to do this without having to make a git
> repository ? What I would like is something like this:
>
> > (package
> > (name "script1")
> > (version "0.0.0")
> > (source (LOCAL-DIR "/path/to/scripts/"))
> > (build-system trivial-build-system))
>
> and then copy the guile script to /bin using the trivial build-system.
>
> I guess what I'm looking for is a function like LOCAL-DIR. It would be
> similar to git-checkout but wouldn't require git. Is there such
> a thing ?
I believe you are looking for (source (local-file ..)), example can be found in
this excellent blog post:
https://guix.gnu.org/en/blog/2023/from-development-environments-to-continuous-integrationthe-ultimate-guide-to-software-development-with-guix/
>
> Cheers,
>
> Théo
>
)t.
--
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 --]
next prev parent reply other threads:[~2023-10-26 14:19 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 [this message]
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
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=ZTp1TiDyDniEI_bW@ws \
--to=wolf@wolfsden.cz \
--cc=help-guix@gnu.org \
--cc=theo.tyburn@posteo.net \
/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.