#14840: SageNB package contains many packages
-------------------------------------+-------------------------------------
Reporter: felixs | Owner: felixs
Type: defect | Status: needs_review
Priority: major | Milestone: sage-7.2
Component: packages: | Resolution:
standard | Merged in:
Keywords: notebook, days77 | Reviewers: Salvatore Stella
Authors: Jeroen Demeyer | Work issues:
Report Upstream: Reported | Commit:
upstream. No feedback yet. | 161ac3ba998689b9a3a3435ed85e4316cd61fb77
Branch: | Stopgaps:
u/jdemeyer/ticket/14840 |
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by jhpalmieri):
Replying to [comment:64 dimpase]:
> Replying to [comment:63 jhpalmieri]:
> > Replying to [comment:62 vbraun]:
> > > I tend to agree that we should just exclude web-based UIs (SageNB +
Jupyter) from the "self-contained tarball" and make them pip-type optional
packages instead. If you don't have internet access then how come you have
a browser installed?
> >
> > Because you live in a third world country and have inconsistent
access? Because you're traveling and want to build Sage while on an
airplane (and without paying the wifi fees)? You can come up with plenty
of reasons.
>
> Inconsistent access is a nightmare if you need to get a large file (e.g.
current Sage source tarball), as opposed to several small files.
Hence tarballs on thumb drives.
> Besides, mind you, much more popular than Sage software distribution
systems, e.g. ones for Python, Haskell, OCaml do require internet access,
by default. Convenience for the majority (and for developers) ought to
come before exotic usage cases.
If/when we make sagenb into an optional or experimental package, I have no
objections to doing the same with these dependencies. But until then, in
what way is including a dozen packages an inconvenience? It doesn't take
up any extra disk space or extra time building Sage since we're already
including them, it just adds a few directories in `build/pkgs`. How is
this more of an inconvenience than requiring internet access during
compilation of Sage?
Replying to [comment:65 vbraun]:
> IMHO those use cases are better served by having a script that downloads
all standard+optional packages. I already have a script where you just
have to
> {{{
> sage-package download :standard: :optional:
> }}}
> to grab them all in one go.
And how are Sage developers supposed to know about this, if they are going
to be traveling and without good internet access for a while? It sounds
like a good idea, but I still don't see what it saves vs. making these
standard Sage packages (for as long as sagenb is a standard Sage package,
but no longer).
--
Ticket URL: <http://trac.sagemath.org/ticket/14840#comment:66>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
