Open krey opened 6 years ago
hopefully https://github.com/NixOS/nixpkgs/pull/33673 will improve the situation
@teto: I see. So in that framework you write the kernels by hand, rather than relying on the installer.
It's not complete yet. Some packages provide kernels (sage for instance) so the framework could accept a list of packages instead. (easier than writing the kernels by oneself)
Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
This is still important to me.
I marked this as stale due to inactivity. → More info
This is still important to me.
I marked this as stale due to inactivity. → More info
Still important
Issue description
When JuniperKernel installs the kernelspec, it uses
$R_HOME
to figure out where the R executable lives.$R_HOME
is set to unwrapped R (see below) which doesn't have any of the packages, so the kernelspec produced is wrong. When used inside jupyter, it will not be able to find Juniper and the kernel will not work.Related: https://github.com/NixOS/nixpkgs/issues/16485#issuecomment-259832281
Steps to reproduce
but that's the wrong R (the unwrapped one). The right one is:
Further thoughts
One of the key things
rWrapper
does is to set$R_LIBS_SITE
:It would be cool if this was exposed in some way and I could do
source ${my-R-env}/bin/activate
.My current workaround is unpleasant
Technical details
"x86_64-linux"
Linux 4.14.32, NixOS, 18.03.131807.489a14add9a (Impala)
yes
no
nix-env (Nix) 2.0
"nixos-18.03, nixos-unstable, nixpkgs-unstable"
""
/nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs