On Thu, 27 Feb 2020 at 20:39, Ricardo Wurmus <rek...@elephly.net> wrote: > zimoun <zimon.touto...@gmail.com> writes: > > On Thu, 27 Feb 2020 at 19:43, Vincent Legoll <vincent.leg...@gmail.com> > > wrote: > >> On Thu, Feb 27, 2020 at 7:20 PM zimoun <zimon.touto...@gmail.com> wrote:
> >> > Because other kernels are named: python-ipykernel or ruby-iruby. > >> > Another: python-pari-jupyter. > >> > And another other: jupyter-guile-kernel. > >> > Well, there is no real convention yet, if I understand correctly. > >> > > >> > A good move should to start a gnu/packages/jupyter.scm to put all the > >> > Jupyter related machinery inside... I do not know. > >> > >> Maybe we can help them show up properly in guix search results, like > >> adding what could be missing in description. > > > > Hum? I am not convinced that something is missing in the > > description... I mean "guix search jupyter kernel | less" does already > > the job, IMHO. > > What should be missing is some convention in the naming scheme; and it > > seems easier to force a convention when all the same related packages > > live in the same file. > > The name r-irkernel follows the R package convention; a similar reason > applies to python-ipykernel and ruby-iruby. Yes, I know. :-) Well, "it seems easier to force a convention when all the same related packages live in the same file" so the current convention is the cran.scm, ruby.scm or python.scm one. And I was suggesting to move the packages related to Jupyter to its own module using the convention 'jupyter-' convention, e.g., 'jupyter-irkernel'. And even a more uniformized naming scheme between all the kernels. As I said, I do not know if it is a good idea or not. :-) Cheers, simon
