#15816: binary package rebuilds packages after harmless ticket checkout/make
-------------------------------------------+------------------------
Reporter: rws | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.2
Component: documentation | Resolution:
Keywords: binary, make, toolchain | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-------------------------------------------+------------------------
Changes (by jdemeyer):
* component: build => documentation
Comment:
Replying to [ticket:15816 rws]:
> How can I avoid this?
You could try simply `./sage -b` instead of `make` to rebuild only the
Sage library. However, there is no guarantee that this will work.
> It's supposed to be a complete binary...
It is, but it can obviously not contain stuff from tickets that have not
been merged yet.
> Alternatively, give more information in the docs on what the user has to
expect with the binary distribution.
The same as with the source distribution, if you change package versions,
those new versions will need to be built.
Where do you think we should add this documentation?
[http://www.sagemath.org/doc/installation/binary.html Here] perhaps?
--
Ticket URL: <http://trac.sagemath.org/ticket/15816#comment:4>
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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.