#13574: sage-spkg: check much earlier whether package is already installed
----------------------------------+-----------------------------------------
Reporter: jdemeyer | Owner: GeorgSWeber
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.5
Component: build | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Jeroen Demeyer | Merged in:
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by jdemeyer):
Replying to [comment:5 jhpalmieri]:
> When looking for the spkg in cases 2a or 3, why not look in
spkg/installed instead of spkg/standard and spkg/optional?
Mainly, I simply didn't want to change the functionality of
{{{
./sage -f foo
}}}
It's hard to tell which behaviour would be the most expected when doing
{{{
./sage -i mpir
}}}
in the case that mpir is already installed, but no local mpir package
exists in `spkg/`. Should it re-install the installed version or should
it download the latest online version?
If you look in `installed/`, then
{{{
./sage -i mpir
}}}
is going to fail in a lot more cases (it needs to download the exact
version, which might not be found). So maybe I prefer to increase the
chances of success, even if a different version might be installed. That
means, don't consider `installed/`.
In any case, {{{./sage -i}}} and {{{./sage -f}}} should be consistent, the
version cannot depend on whether `-f` was given.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13574#comment:10>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
