Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create an octave package for easy installation within octave itself #9

Open
rapgenic opened this issue Jan 30, 2021 · 2 comments
Open
Assignees
Labels
what/distrib 📦 Software distribution/packaging

Comments

@rapgenic
Copy link
Collaborator

Should be able to install with

pkg install xeus-octave

Octave package should provide a function to register the kernel in the system and a function to start the kernel itself (useful to avoid having a binary xeus-octave file and to rely only on octave binary).

@rapgenic rapgenic added type/planning 📑 Internal organization issues what/distrib 📦 Software distribution/packaging labels Jan 30, 2021
@rapgenic rapgenic self-assigned this Jan 30, 2021
@rapgenic rapgenic changed the title Create an octave package for easy installation within octave itselfq Create an octave package for easy installation within octave itself Jan 30, 2021
@AntoinePrv AntoinePrv removed the type/planning 📑 Internal organization issues label Sep 21, 2022
@SylvainCorlay
Copy link
Member

This sounds challenging because the xoctave binary actually embeds octave... However, we may be able to get away with the same approach we did to make a PyPI package for xeus-python, which is to have a flavor of the package that loads as an extension, and is started from octave.

Some pointer if one is interested

@rapgenic
Copy link
Collaborator Author

Hi, chiming in again to add a few information I did not write in this issue

My original idea was not to make xeus-octave as an extension to octave: i.e. octave starts and loads the kernel.

Instead the idea was to create the xeus-octave package as a simple installer, which would download and build the sources of xoctave, put it in some known location and then create a simple kernelspec file in the appropriate place that would run xoctave as it's done now.

The only difference would've been that the installation happens through octave and in a way the octave users are familiar with, with the possibility to avoid conda/mamba etc which requires some time to setup if you're not a frequent user

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
what/distrib 📦 Software distribution/packaging
Projects
None yet
Development

No branches or pull requests

3 participants