From: james <james@jamescm.co.uk>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Scripting for installing a module
Date: Sun, 3 Jul 2022 08:37:16 +0100 [thread overview]
Message-ID: <20220703073716.afzy7e4srw6hbg54@arch-surface> (raw)
In-Reply-To: <7c8a83de-85d3-60b3-eb0d-98e54ba27316@gmail.com>
On 22/07/02 02:09pm, Matt Wette wrote:
> Another option is some variant of
>
> $ sudo cp xyz/file.scm `guile -c '(display
> (%global-site-dir))'`/xyz/file.scm
>
> On 7/1/22 10:15 AM, James Crake-Merani wrote:
> > guile -c '(display (%global-site-dir))'Hello,
> >
> > I was just wondering what approach people tend to take when writing a script which installs a module onto the load-path. I understand this path might be different on different machines so how do you make sure the module is installed in the right path? Would you use something like a Makefile?
> >
> > Thanks.
> >
>
>
Hi,
Something like that would probably work as well. I might give it a go.
Thanks for your response.
prev parent reply other threads:[~2022-07-03 7:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 17:15 Scripting for installing a module James Crake-Merani
2022-07-01 19:50 ` Jérémy Korwin-Zmijowski
2022-07-02 6:32 ` James Crake-Merani
2022-07-02 7:11 ` adriano
2022-07-02 8:46 ` James Crake-Merani
2022-07-02 19:43 ` Zelphir Kaltstahl
2022-07-03 7:35 ` James Crake-Merani
2022-07-03 16:52 ` Zelphir Kaltstahl
2022-07-05 8:14 ` Munyoki Kilyungi
2022-07-05 9:46 ` James Crake-Merani
2022-07-02 21:09 ` Matt Wette
2022-07-03 7:37 ` james [this message]
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220703073716.afzy7e4srw6hbg54@arch-surface \
--to=james@jamescm.co.uk \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
/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).