From: Ricardo Wurmus <rekado@elephly.net>
To: Julien Lepiller <julien@lepiller.eu>
Cc: anothersms@gmail.com, 36856@debbugs.gnu.org
Subject: [bug#36856] build: Add julia-build-system
Date: Tue, 30 Jul 2019 16:33:03 +0200 [thread overview]
Message-ID: <87o91b619c.fsf@elephly.net> (raw)
In-Reply-To: <1DBAF4CE-8BA5-43EF-9CFE-5A73FB8118EB@lepiller.eu>
Julien Lepiller <julien@lepiller.eu> writes:
> Le 30 juillet 2019 16:11:19 GMT+02:00, Ricardo Wurmus <rekado@elephly.net> a écrit :
>>
>>Nicolò Balzarotti <anothersms@gmail.com> writes:
>>
>>> 3. By adding a simple startup.jl script, inspired by what emacs does.
>>This
>>> is simplified so I'm not sure it works for every corner case.
>>> #+begin_src julia
>>> let paths = [expanduser("~/.guix-profile"),
>>"/run/current-system/profile"]
>>> ("GUIX_ENVIRONMENT" in keys(ENV)) && push!(paths,
>>> ENV["GUIX_ENVIRONMENT"])
>>> empty!(LOAD_PATH)
>>> push!.(Ref(LOAD_PATH), joinpath.(paths, "share/julia/packages/"))
>>> push!(LOAD_PATH, "@stdlib")
>>> push!.(Ref(DEPOT_PATH), joinpath.(paths, "share/julia/"))
>>> nothing
>>> end
>>> #+end_src
>>
>>Could this perhaps be handled by a profile hook that is included only
>>when the profile manifest contains a julia package?
>
> Or simply with an environment variable? GUIX_JULIA_PATH or something?
If this is the route you go down, please ensure that it can be used as a
search path with more than one directory. This would make it possible
to extend a Julia environment with the contents of more than one
profile.
--
Ricardo
next prev parent reply other threads:[~2019-07-30 14:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 12:49 [bug#36856] build: Add julia-build-system Nicolò Balzarotti
2019-07-30 14:08 ` Ricardo Wurmus
2019-07-30 14:11 ` Ricardo Wurmus
2019-07-30 14:23 ` Julien Lepiller
2019-07-30 14:33 ` Ricardo Wurmus [this message]
2019-07-30 16:02 ` Nicolò Balzarotti
2019-08-03 10:03 ` Nicolò Balzarotti
2019-08-03 10:04 ` Nicolò Balzarotti
2019-09-04 20:21 ` bug#36856: " Julien Lepiller
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=87o91b619c.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=36856@debbugs.gnu.org \
--cc=anothersms@gmail.com \
--cc=julien@lepiller.eu \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).