#15580: Integrate prereq in the new build system
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-6.1
Component: distribution | Resolution:
Keywords: | Merged in:
Authors: R. Andrew Ohana, | Reviewers: R. Andrew Ohana
Jeroen Demeyer | Work issues:
Report Upstream: N/A | Commit:
Branch: | 19d5a15ba83c7861237be766420541bb783ec34f
u/jdemeyer/ticket/15580 | Stopgaps:
Dependencies: #15596 |
-------------------------------------+-------------------------------------
Comment (by jdemeyer):
Replying to [comment:46 vbraun]:
> I don't like the fact that I can't test the updated tarball on the
buildbot without bumping the version. This slows down the release process
as I have to bump version and re-run the buildbot.
I thought you were using a private git repo for the buildbot? In that
case, you could easily do the version bump only in your private repo.
Alternatively, point `$SAGE_UPSTREAM` to a place you control.
My philosophy with the buildbot was to always test the '''exact''' source
tarball that I would release. If you're testing first, then changing the
version number, then `sdist`, something could go wrong in those last two
steps and you would never notice.
And yes, there has been at least one bug which dependended on the length
of the Sage version number, so it can happen.
--
Ticket URL: <http://trac.sagemath.org/ticket/15580#comment:47>
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.
