-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
sage_bootstrap: Add command "sage -package list --output={install-requires,requirements,pipfile,debian,....}" #29041
Comments
comment:2
This is what it could look like - just for a small handful of packages for now New commits:
|
Commit: |
comment:3
The |
Author: Matthias Koeppe |
comment:6
I see that only few packages, e.g. pillow, are mentioned in the branch. Are they there as an example? |
comment:7
Yes, it's an initial example. More can be added on this ticket and/or on follow up tickets. It may be the most efficient to first put this infrastructure (and the one for Debian) in place and then do invidual packages one by one to determine useful version bounds. |
comment:8
how is it going to play out with version constraints in spkg-configure.m4 files? |
comment:9
So far there are no |
comment:10
Basically |
comment:11
@embray If you have time - this ticket is waiting for review. |
comment:12
Similar to what I wrote on #26964, I don't think this should be done in the This could be done by |
comment:13
See my comments on #26964. |
Dependencies: #29233 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Changed commit from |
Changed author from Matthias Koeppe to none |
This comment has been minimized.
This comment has been minimized.
Changed work issues from redo on top of #29950 to none |
This comment has been minimized.
This comment has been minimized.
Changed keywords from none to sd111 |
comment:37
Hoping we can make progress on this ticket this week - https://wiki.sagemath.org/days111 |
This comment has been minimized.
This comment has been minimized.
comment:39
Rewriting tools used in the bootstrap phase in Python would also be useful for developing on Windows |
comment:40
hmm, what is so problematic about Windows here? Even if one talks about native, non-cygwin, it is still perfectly possible to run bash etc. |
This comment has been minimized.
This comment has been minimized.
comment:42
Setting new milestone based on a cursory review of ticket status, priority, and last modification date. |
comment:44
Setting a new milestone for this ticket based on a cursory review. |
We extend the
sage_bootstrap
package to add the commands:sage -package list --output=install-requires PACKAGES...
(for sagelib: Generate pyproject.toml and setup.cfg [install_requires], requirements.txt, Pipfile, and src/Pipfile #30913)sage -package list --output=requirements PACKAGES...
sage -package list --output=pipfile PACKAGES...
sage -package list --output=debian PACKAGE...
etc. (taking over the functionality of the shell scriptbuild/bin/sage-get-system-packages
.)They generate text output in the format of
setup.cfg [options] install_requires=
,requirements.txt
, andPipfile
; or a list of system packagesbootstrap
can use these commands to generate these files forbuild/pkgs/sagelib/src/
orsrc
. They are deleted bymake bootstrap-clean
.References:
CC: @seblabbe @dimpase @embray @vbraun @kiwifb @tobihan @tobiasdiez
Component: build
Keywords: sd111
Issue created by migration from https://trac.sagemath.org/ticket/29041
The text was updated successfully, but these errors were encountered: