From: Sharlatan Hellseher <sharlatanus@gmail.com>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 46333@debbugs.gnu.org
Subject: bug#46333: sbcl-common-lisp-jupyter does not install kernel.json
Date: Wed, 19 May 2021 22:23:14 +0000 [thread overview]
Message-ID: <CAO+9K5qb=f+F5dSujm+8FLCjigcTXSyBbwRfLN=fKZ2GsSDjsg@mail.gmail.com> (raw)
In-Reply-To: <87lf8cugh1.fsf@kitej>
Hi,
I've checked the r-irkernel and it's coping existing kernelspec ,
which is not useful in this case.
As Guillaume mentioned we could tweak it before installation phase by
using cl-jupyter:install, so here is my draft:
--8<---------------cut here---------------start------------->8---
(arguments
`(#:phases
(modify-phases %standard-phases
(add-before 'install 'generate-kernelspec
(lambda* (#:key outputs #:allow-other-keys)
(let* ((out (assoc-ref outputs "out"))
(kernelspec (string-append out
"/share/cl-jupyter/kernelspec")))
(mkdir-p kernelspec)
(invoke "sbcl"
"--eval" "\"(require :asdf)\""
"--eval" "\"(require :common-lisp-jupyter)\""
"--eval"
(string-append
"\"(cl-jupyter:install"
":bin-path" (string-append
(assoc-ref %build-inputs "sbcl")
"/bin/sbcl")
":prefix" out ")\"")
"--eval" "\"(exit)\""))
#t))
(add-after 'install 'install-kernelspec
(lambda* (#:key outputs #:allow-other-keys)
(let ((out (assoc-ref outputs "out"))
(kernelspec (string-append out
"/share/cl-jupyter/kernelspec")))
(invoke "jupyter" "kernelspec" "install"
"--name" "cl-jupyter"
"--prefix" out
kernelspec)
#t))))))
--8<---------------cut here---------------end--------------->8---
But there could be a potential blocking issue with :prefix key
https://github.com/yitzchak/common-lisp-jupyter/issues/78
On Tue, 18 May 2021 at 16:58, Guillaume Le Vaillant <glv@posteo.net> wrote:
>
> Hi Jack,
>
> I guess it will be easier to just add a phase writing the "kernel.json"
> file in the right place. In this build phase, to know if the package is
> being built for SBCL or ECL, the '(%lisp-type)' function that will
> return "sbcl" or "ecl" can be used. There's an example in the
> sbcl-trivial-backtrace package.
--
… наш разум - превосходная объяснительная машина которая способна
найти смысл почти в чем угодно, истолковать любой феномен, но
совершенно не в состоянии принять мысль о непредсказуемости.
next prev parent reply other threads:[~2021-05-19 22:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 19:44 bug#46333: sbcl-common-lisp-jupyter does not install kernel.json Jack Hill
2021-05-18 16:12 ` Jack Hill
2021-05-18 16:58 ` Guillaume Le Vaillant
2021-05-19 22:23 ` Sharlatan Hellseher [this message]
2021-05-24 21:28 ` Sharlatan Hellseher
2021-05-25 15:40 ` Guillaume Le Vaillant
2021-06-08 14:48 ` bug#46333: Install Command Line Tarn Burton
2021-06-14 15:21 ` bug#46333: Typos Tarn Burton
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='CAO+9K5qb=f+F5dSujm+8FLCjigcTXSyBbwRfLN=fKZ2GsSDjsg@mail.gmail.com' \
--to=sharlatanus@gmail.com \
--cc=46333@debbugs.gnu.org \
--cc=glv@posteo.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 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).