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
"empty" .spkg files in binary builds confusing #6822
Labels
Comments
comment:1
See this sage-devel thread. It was where this issue started. |
This comment has been minimized.
This comment has been minimized.
Attachment: trac_6822-root.patch.gz |
Attachment: trac_6822-scripts.patch.gz |
This comment has been minimized.
This comment has been minimized.
Changed keywords from none to bdist spkg |
Author: John Palmieri |
comment:3
Here's a simple-minded approach. |
Reviewer: Jeroen Demeyer |
comment:5
Probably good, but we should only merge this with #13574. |
Dependencies: #13574 |
Merged: sage-5.5.beta1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For binary distributions, we ship fake .spkg files in spkg/standard. This was introduced to work around some bug but that bug doesn't exist anymore. So stop shipping those fake packages.
Apply:
Depends on #13574
CC: @jhpalmieri
Component: distribution
Keywords: bdist spkg
Author: John Palmieri
Reviewer: Jeroen Demeyer
Merged: sage-5.5.beta1
Issue created by migration from https://trac.sagemath.org/ticket/6822
The text was updated successfully, but these errors were encountered: