From: Suhail Singh <suhailsingh247@gmail.com>
To: 74845@debbugs.gnu.org
Cc: Philip McGrath <philip@philipmcgrath.com>
Subject: bug#74845: Guix racket: binaries installed via "raco pkg install" missing --config directory
Date: Thu, 12 Dec 2024 22:07:01 -0500 [thread overview]
Message-ID: <87ttb8b7sa.fsf@gmail.com> (raw)
Hello Guix,
Currently, binaries installed via "raco" (included in Guix's "racket"
package) don't include the -G / --config configuration option specifying
the "Main configuration directory". This is problematic.
Specifically, when installing "rash" via raco using the below:
#+begin_src sh
raco pkg install rash
#+end_src
The resulting rash-repl binary is missing the -G configuration option in
the call to the racket binary. Invoking the installed rash-repl binary
results in the following error:
#+begin_src sh
standard-module-name-resolver: collection not found
for module path: (lib "rash/repl.rkt")
collection: "rash"
in collection directories:
${HOME}/.local/share/racket/8.14/collects
/gnu/store/vn20i9xk22czljr9drwzwpgw209l49s8-racket-vm-cs-8.14/opt/racket-vm/collects/
#+end_src
Adding the -G configuration option similar to what's included in the
"raco" script itself, fixes the above error.
The executable scripts (at least on linux) seem to be generated via
make-unix-launcher in ./racket/collects/launcher/launcher.rkt . What's
unclear is the best way in which to address this issue. For one thing,
the -G configuration option in the "raco" script (which addressed the
issue in the rash-repl script above) references the store location of
the racket guix package. However, the launcher.rkt (which contains the
definition of make-unix-launcher) file is compiled as part of
racket-vm-cs (which is an input of racket).
--
Suhail
next reply other threads:[~2024-12-13 3:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 3:07 Suhail Singh [this message]
2024-12-16 20:25 ` bug#74845: [PATCH] gnu: racket: Ensure package launchers reference config directory Suhail Singh
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=87ttb8b7sa.fsf@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=74845@debbugs.gnu.org \
--cc=philip@philipmcgrath.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.
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.