On Fri, Aug 14, 2015 at 12:48 PM, Alberto Planas
On Friday, August 14, 2015 10:38:39 AM Todd Rme wrote:
Does this approach seem reasonable to everyone? Comments, criticisms, suggestions?
Your proposal is quite outstanding, and can deliver a very high quality jupyter package for openSUSE. My approach will be much more simplistic:
* python-jupyter_ipython: contain gentuils, traitles, core, client, console and ipykernel (?). This will provide the classical console iPython.
* python-jupyter_qtconsole: depends on python-jupyter_ipython
* python-jupyter_notebook: contains also nbformat
* python-jupyter_nbconvert: Good idea to put it alone, AFAIK this will depend on pandoc and haskell
I am not sure that many people will demand python-traitlets apart from juputer itself.
Anyway, your solution is quite superior.
Sorry, perhaps I wasn't clear. The problem is that every package I listed is a separate upstream package, with its own tarball, own pypi page (or two), own github project, etc. So ipython_genutils is one upstream package, traitlets is another upstream package, nbformat is another, notebook is another, etc. There is no longer any individual upstream "jupyter" package. Well, there is, but it is just a metapackage, it contains essentially no source code itself, it just depends on these other packages (or depends on one of these packages, which in turn depends on another). So I am just following the upstream package breakdown. One tarball per rpm. The only thing really up to us is what we call these packages, and how we organize them across the different openSUSE repositories. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org