-
-
Notifications
You must be signed in to change notification settings - Fork 453
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
bootstrap, src/doc/Makefile: Remove use of the SAGE_ROOT/sage script #33852
Comments
Commit: |
Last 10 new commits:
|
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.
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits: |
comment:17
I found it a bit hard to figure out what came from #33740 and what is this ticket :( Once I get past that issue, I agree with the changes. It is much cleaner and simpler. May not go far enough from a sage-on-gentoo point of view (I will still patch but we had that discussion |
comment:18
Replying to @kiwifb:
Yes but what would be its dependencies? |
comment:19
Replying to @mkoeppe:
I am not sure I follow. It doesn't need to have dependencies or have I forgotten something fundamental about makefiles. |
comment:20
In that case it would never be updated, which can't be right |
comment:21
Replying to @mkoeppe:
Thank you for reminding me of some essentials :) I'd like to brush it off as it being too early in the morning to make a proper comment but I think that's just part of a pattern where I am too deep on the packager side, and thinking of workflow in which ultimately, makefile such as this one are "single use", and when something doesn't work you just restart from the top because you need the flow to be right. I am not spending enough time on the pure dev side, that's what |
comment:22
I think this looks okay, too. François, do you agree with a positive review? |
comment:23
Yes, let's get it in the next beta. |
Reviewer: John Palmieri, François Bissey |
comment:25
Thanks! |
Changed branch from u/mkoeppe/bootstrap__remove_use_of_the_sage_root_sage_script to |
We change the
bootstrap
scripts so that they invokebuild/bin/sage-package
directly instead of going through theSAGE_ROOT/sage
script.This is faster and also more robust because it separates build phases better by eliminating the (unnecessary) use of
configure
-generated files such assrc/bin/sage-src-env-config
.We also move the generation of
src/doc/en/reference/repl/options.txt
(by callingsage -advanced
) from bootstrap time tosrc/doc/Makefile
. The information displayed there depends on what packages are installed, so running it at bootstrap time was not correct.Depends on #33740
CC: @jhpalmieri @tobiasdiez @orlitzky @dimpase @kiwifb
Component: scripts
Author: Matthias Koeppe
Branch/Commit:
67c8238
Reviewer: John Palmieri, François Bissey
Issue created by migration from https://trac.sagemath.org/ticket/33852
The text was updated successfully, but these errors were encountered: