New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add William's "personal souped up version of sage -bdist" to Sage #4666
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
People get very confused by the generic names and end up downloading completely inappropriate releases, so I am making this a 3.3 blocker since I will be fixing this. Cheers, Michael |
comment:3
Reassign it to 3.3 again. Cheers, Michael |
comment:4
Better luck in 3.4.1. Cheers, Michael |
comment:6
If we've released for months and months without fixing this, it doesn't make sense to keep it as a blocker. |
This comment has been minimized.
This comment has been minimized.
Author: William Stein |
Changed author from William Stein to William Stein, Jeroen Demeyer |
This comment has been minimized.
This comment has been minimized.
comment:8
Attachment: botdist.py.gz |
comment:14
A lot of this is now in |
comment:15
Replying to @kcrisman:
That's more a question for the current release manager. Like I mentioned on the ticket, I was using William's script to generate binaries, but if Volker no longer uses this, we might as well close this ticket as "wontfix". |
comment:16
Replying to @jdemeyer:
Volker? |
comment:17
I'm not using this script. Labeling binary tarballs by distribution might be worthwile, though. I'm not sure if the current bdist script does that. Note that the buildbots rename the binary tarball as one of the buildsteps. |
Reviewer: Jeroen Demeyer |
Changed author from William Stein, Jeroen Demeyer to none |
The buildbots are using a script (originally written by William and edited by me) to produce the binaries. It automatically builds a "Mac App" on OS X and chooses a meaningful name for the binary.
Some version of this script should be added to Sage itself, I propose to call it
sage-autobdist
. Thensage-bdist
can handle the low-level stuff of actually building the binary.I'm adding the script as reference, but it needs some work to integrate it in Sage.
CC: @jhpalmieri @vbraun
Component: build
Reviewer: Jeroen Demeyer
Issue created by migration from https://trac.sagemath.org/ticket/4666
The text was updated successfully, but these errors were encountered: