From: "Nicolò Balzarotti" <anothersms@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 36856@debbugs.gnu.org
Subject: [bug#36856] build: Add julia-build-system
Date: Tue, 30 Jul 2019 16:02:39 +0000 [thread overview]
Message-ID: <CAO7Ox=YT10fsg+tsEeCwR+MkkJaDy6to6CpjxzcnSJObH2dsUQ@mail.gmail.com> (raw)
In-Reply-To: <87o91b619c.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]
Thanks for the quick response!
Well, the environment variable JULIA_LOAD_PATH (that inside julia is just
LOAD_PATH) works exactly like that (is a column-concatenated path list). It
just needs the special ":@stdlib" path to let julia find its standard
libraries.
Example:
> JULIA_LOAD_PATH=/my/new/path/:/profile/path/:@stdlib julia --startup=no
-E 'LOAD_PATH'
["/my/new/path/", "/profile/path/", "@stdlib"]
Is setting this variable from guix fine, or we need a special
GUIX_SOMETHING variable?
Where exactly should I set this?
Thanks
Il giorno mar 30 lug 2019 alle ore 14:33 Ricardo Wurmus <rekado@elephly.net>
ha scritto:
>
> 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
>
>
[-- Attachment #2: Type: text/html, Size: 2929 bytes --]
next prev parent reply other threads:[~2019-07-30 16:04 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
2019-07-30 16:02 ` Nicolò Balzarotti [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAO7Ox=YT10fsg+tsEeCwR+MkkJaDy6to6CpjxzcnSJObH2dsUQ@mail.gmail.com' \
--to=anothersms@gmail.com \
--cc=36856@debbugs.gnu.org \
--cc=rekado@elephly.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.