> On 19/05/2018, at 18:30, Nils Bruin <nbr...@sfu.ca> wrote:
>
> On Thursday, May 17, 2018 at 1:01:21 AM UTC-7, François Bissey wrote:
> Actually in sage-on-gentoo I reduced that quite a bit. In vanilla we have
> "argv": ["/home/fbissey/sandbox/git-fork/sage-8.3.b0/local/bin/sage",
> "--python", "-m", "sage.repl.ipython_kernel", "-f", "{connection_file}”]
> That is, sage-devs go to quite some lengths to launch sage’s python with the
> sage
> ipython_kernel module.
>
> In sage-on-gentoo I just do this at the moment:
> {"argv": ["python2.7", "-m", "sage.repl.ipython_kernel", "-f",
> "{connection_file}”]
>
> François
>
> so, am I right in concluding that distribution packages patch this anyway
> and that we can therefore safely put $SAGE_ROOT/sage in kernel.json by
> default?
>
I don’t know what other distros do. The stuff in vanilla sage feels overkill to
me,
even I have a good idea of why it was done that way.
But in a general way I am opposed to addition of SAGE_ROOT anywhere that is
not the build system. Including SAGE_ROOT here will quite likely to annoy
people working on VPATH build of sage (i.e. build where SAGE_LOCAL is not
actually inside SAGE_ROOT and nor should you assume it).
François
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
