-
-
Notifications
You must be signed in to change notification settings - Fork 454
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
Remove obsolete scripts from src/bin/ #29383
Comments
Commit: |
comment:3
remind me, what's the new way to make user packages for Sage? |
comment:4
Create the appropriate subdirectory of |
comment:5
But there is no non-deprecated way for someone to create a standalone package which is not part of Sage, I think. |
comment:6
That's right |
comment:7
It works for me. Is it okay to remove the only way to create standalone user packages, even if it is deprecated? It's not even documented anywhere. I say we merge this. Or do we need to ask on sage-devel? |
comment:8
The discussion on sage-devel happened already, leading to the deprecatIon. |
Reviewer: Dima Pasechnik |
comment:9
ok - I assume you checked that this is not in docs any more, either. |
comment:10
Thanks! |
comment:13
Replying to @jhpalmieri:
You're right. |
Changed branch from u/mkoeppe/remove_obsolete_scripts_from_src_bin_ to |
sage-README-osx.txt
# see update installation guide #25995, Move non-scripts of src/bin/ elsewhere (and also move their install location) #21570sage-pkg
# a script to create old-style spkgssage-unzip
# unused(Part of #21559.)
CC: @jhpalmieri @dimpase @orlitzky
Component: scripts
Author: Matthias Koeppe
Branch/Commit:
f7f34ff
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/29383
The text was updated successfully, but these errors were encountered: