Closed seidewitz closed 4 years ago
To clarify, are you asking for the Jupyter installer, as-is in this branch, to be patched for this release or for this change to be done in the source repo for subsequent releases?
To clarify, are you asking for the Jupyter installer, as-is in this branch, to be patched for this release or for this change to be done in the source repo for subsequent releases?
Good question.
The source for the installer should be updated for subsequent releases, and then the Jupyter install directory should be updated in this repository with the new version. However, it is not clear to me what the "source repo" is for the installer. Is it in the org.omg.sysml.jupyter
project in the SysML v2 Pilot Implementation? I don't see the install scripts there.
If you have suggests on the best way to handle this, let me know.
@seidewitz been mulling over options. The leading one is to publish the kernel as a Conda package like the rest of the Jupyter environment where installation would be conda install -c conda-forge isysml
and it would pull from the Conda repository. This would mean that the directory @ https://github.com/Systems-Modeling/SysML-v2-Release/tree/ST6RI-259/install/jupyter/sysml would no longer need to exist and the duplication would be gone. This would be analogous to using Eclipse update sites.
If that sounds good to you, I can proceed with setting that up and updating the installers/instructions.
@ivan-gomes Yes, proceed with the Conda install approach.
@manasbajaj
The intent of ST6RI-259 was to move the kerml and sysml model projects into a separate repository. However, this might also be an opportunity to manage other things that we put into the public releases. So I have named the new repository SysML-v2-Release and I have also included the training and spec PDFs and the Eclipse and Jupyter installers.
When can update this when we do a release, and then attach zips for download to the release as usual on GitHub. This could replace having to stage everything on Google Drive each time.
Does that make sense to you?
@ivan-gomes
I unzipped the Jupyter installation archive into the
install\jupyter
directory. This still includes a copy of the fullsysml.library
directory. Can you update the installer to use thesysml.library
project at the top-level in the repository? This would perhaps make the Jupyter installation less self-contained if we wanted to zip it separately, but it seems better to have only one copy of the library files in the repository.(Note also that the README files are also not all updated yet. So this should be considered an in-progress review.)