#7544: downloading packages with sage-spkg
----------------------+-----------------------------------------------------
Reporter: mvngu | Owner: tbd
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.3
Component: misc | Keywords:
Work_issues: | Author: Minh Van Nguyen
Upstream: N/A | Reviewer:
Merged: |
----------------------+-----------------------------------------------------
Changes (by newvalueoldvalue):
* status: new => needs_review
* author: => Minh Van Nguyen
Old description:
> At least with Sage 4.3.alpha0, doing
> {{{
> ./sage -i <url>/<package>-x.y.z.spkg
> }}}
> won't download the given package name if `<url>/<package>-x.y.z.spkg` is
> a URL other than that on the Sage website. The issue was reported in
> [http://groups.google.com/group/sage-
> devel/browse_thread/thread/0df661d74b620901 sage-devel].
> [[BR]][[BR]]
>
> When one issues the following command:
> {{{
> sage -i <package>
> }}}
> then if <package> is already installed, one expects Sage to report that
> and quit trying to install `<package>`. In case, one really wants to
> install <package> regardless of whether or not `<package>` is already
> installed on one's local Sage installation, the following incantation
> should be used:
> {{{
> sage -f <package>
> }}}
> The documentation for installing an spkg, as output by "`sage -h |
> -advanced`", clearly documents the behaviour of the options "`-i`" and
> "`-f`" so I think we need to document the specific values that
> `<package>` can take.
> [[BR]][[BR]]
>
> Suppose for discussion that `<package>-x.y.z.spkg` is a Sage package,
> whether that be in the standard, optional or experimental repository. At
> the very least, one expects both of the options "`-i`" and "`-f`" to
> consider the following as valid values:
>
> 1. `<package>-x.y.z`, i.e. the name of the package plus the package's
> version numbers.
> 1. the full name `<package>-x.y.z.spkg`, i.e. the name of the package in
> addition to the version numbers and the ".spkg" extension.
> 1. `<URL>/<package>-x.y.z.spkg`, i.e. the full URL where the package is
> hosted. This can be a URL on the Sage website or somewhere else.
> 1. `/path/to/<package>-x.y.z.spkg`, i.e. the package is found somewhere
> in your file system and you're giving an absolute or relative path to the
> package.
>
> At least with Sage 4.3.alpha0, almost all of the above four values are
> valid. The exception is the reported issue, i.e.
> `<URL>/<package>-x.y.z.spkg` cannot be a URL other than that on the Sage
> website. Incidentally, with Sage 4.3.alpha0 one can also do "`sage -i
> <package>`", where `<package>` is just the package name without the
> version numbers nor the ".spkg" extension. I think all of the above four
> values should be valid and the install script should process them as
> valid values.
New description:
At least with Sage 4.3.alpha0, doing
{{{
./sage -i <url>/<package>-x.y.z.spkg
}}}
won't download the given package name if `<url>/<package>-x.y.z.spkg` is a
URL other than that on the Sage website. The issue was reported in
[http://groups.google.com/group/sage-
devel/browse_thread/thread/0df661d74b620901 sage-devel].
[[BR]][[BR]]
When one issues the following command:
{{{
sage -i <package>
}}}
then if <package> is already installed, one expects Sage to report that
and quit trying to install `<package>`. In case, one really wants to
install <package> regardless of whether or not `<package>` is already
installed on one's local Sage installation, the following incantation
should be used:
{{{
sage -f <package>
}}}
The documentation for installing an spkg, as output by "`sage -h |
-advanced`", clearly documents the behaviour of the options "`-i`" and
"`-f`" so I think we need to document the specific values that `<package>`
can take.
[[BR]][[BR]]
Suppose for discussion that `<package>-x.y.z.spkg` is a Sage package,
whether that be in the standard, optional or experimental repository. At
the very least, one expects both of the options "`-i`" and "`-f`" to
consider the following as valid values:
1. `<package>-x.y.z`, i.e. the name of the package plus the package's
version numbers. This should download the corresponding package from the
Sage website.
1. the full name `<package>-x.y.z.spkg`, i.e. the name of the package in
addition to the version numbers and the ".spkg" extension. This also
should download the corresponding package from the Sage website.
1. `<URL>/<package>-x.y.z.spkg`, i.e. the full URL where the package is
hosted. This can be a URL on the Sage website or somewhere else.
1. `/path/to/<package>-x.y.z.spkg`, i.e. the package is found somewhere
in your file system and you're giving an absolute or relative path to the
package.
At least with Sage 4.3.alpha0, almost all of the above four values are
valid. The exception is the reported issue, i.e.
`<URL>/<package>-x.y.z.spkg` cannot be a URL other than that on the Sage
website. Incidentally, with Sage 4.3.alpha0 one can also do "`sage -i
<package>`", where `<package>` is just the package name without the
version numbers nor the ".spkg" extension. I think all of the above four
values should be valid and the install script should process them as valid
values.
--
Comment:
The patch `trac_7544-sage-spkg.patch` should be applied to the script
repository. It changes the file `SAGE_ROOT/local/bin/sage-spkg` so that
one can install an spkg by passing any of the above four values to the
options "`-i`" and "`-f`".
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7544#comment:1>
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.
