This could mean one of the following:
When building:
[a] Make external Jupyter a prerequisite.
[b] If external Jupyter found, install Sage kernel for it,
otherwise print information about how to install Jupyter
and how to install Sage kernel for it later.
[c] If external Jupyter found, install Sage kernel for it,
otherwise build it.
For binaries:
[z] Make external Jupyter a prerequisite for running Sage;
at first start, install Sage kernel to external Jupyter.
[y] If external Jupyter found at first start, install Sage kernel for it,
otherwise print information about how to install Jupyter
and how to install Sage kernel for it later.
[x] Keep shipping Jupyter in binaries.
I don't think we want [a] or [z].
When building I could see [b] or [c].
For binaries I could see [y] or [x].
Some distributions make the Sage kernel an optional install
by providing several packages, like sagemath, sagemath-jupyter,
sagemath-documentation.
Nils has a good point: we need to think about what to do
if a user updates Sage or builds several copies of Sage.
Related:
- How to install sagemath kernel in Jupyter
- sage-devel: Installing sage as a kernel in the system-wide jupyter
- Sage Windows: Include a Sage kernelspec that is
compatible with Windows native Jupyter
- How to install SageMath kernel in Anaconda?