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
Move configuration part of build/make/install to configure #19043
Comments
Commit: |
New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:4
I would be willing to review this. |
Dependencies: #18885 |
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:
|
This comment has been minimized.
This comment has been minimized.
comment:9
Rebased. I know the git history looks funny, but you really should just review the result, not the individual commits. |
comment:10
I don't care about having a "perfect" history (and normally review the final diff from Overall it looks good from my testing. However, I'm not quite sure about this
To make sure I understand correctly, does this mean that anytime we want to do a version bump of packages (or add one), we have to manually run Also is there a reason why you moved the "if root" test lower in the file? I would think we'd want such build failures to happen as early on as possible. |
comment:11
Replying to @tscrim:
Yes.
OK, I see your point. I'd rather make that a separate ticket, there might be other changes to the spkg development guide I want to make.
All releases, beta and stable. So in practice, you only really need to run
There is no real particular reason, it felt more logical to put it where it currently is.
Why? |
comment:12
Replying to @jdemeyer:
Fair enough, but let's make that spkg dev guide update ticket a blocker.
Thanks for the explanation.
I feel that some of those configuration steps could take some time, just to have it fail for an unrelated reason. However I don't really care about this; it was more out of curiosity. |
Reviewer: Travis Scrimshaw |
Changed branch from u/jdemeyer/move_install_to_configure to |
Changed commit from |
comment:15
OSX doesn't build gcc any more with this ticket, but just fails with |
comment:18
I don't understand why |
comment:19
Or anything in your buildbot affecting timestamps as a whole? What happens if you replace |
comment:20
Its the same machine that you also have an account for. It compiles fine without this ticket. If this ticket needs an updated confball then it should be committed, too. The change in confball needs to be in some commit, otherwise the buildbot can't test it. |
comment:22
It's the first time I hear this. I thought that was the job of the release manager when creating the sdist? |
comment:23
I need more information about the buildbot setup, otherwise I don't know what to do. From your logs, it looks like |
Changed branch from |
Commit: |
This comment has been minimized.
This comment has been minimized.
comment:25
Is this what you need? New commits:
|
comment:26
The confball is updated during release but ideally we can test a ticket before the release... The buildbot just pulls the source and runs |
comment:27
Thats not the file:
|
comment:28
I will deal with it on #19266. New commits:
|
Changed branch from u/jdemeyer/4178b80c3ff5ce8e1753bffe48f32dc5bcccb728 to u/jdemeyer/move_install_to_configure |
This comment has been minimized.
This comment has been minimized.
comment:30
Since the confball will be handled on #19266, we're back to positive review (I tested it with the one Jeroen provided after running a checksum fix). |
comment:32
Volker, can you please try to merge this in the next beta? Otherwise there will be a conflict with the |
Changed branch from u/jdemeyer/move_install_to_configure to |
Most of what
build/make/install
does really belongs inconfigure
, in particular creatingbuild/make/Makefile
. This ticket moves that part toconfigure
and adjusts the top-level build system to make this work.There are two advantages:
make
is a lot simpler and hence faster../configure
to configure the list of packages (note that this ticket does not implement that, it just makes it possible to implement that in future tickets)There is an important change for developers: any change to the list or versions of packages will require a run of
./configure
to take effect. Note that./configure
will be re-run automatically if./configure
itself changes, which happens with every Sage version. So there is no need to manually rerun./configure
if you're just switching between versions.Depends on #18885
Depends on #19187
Depends on #19266
Component: build
Author: Jeroen Demeyer
Branch/Commit:
4178b80
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/19043
The text was updated successfully, but these errors were encountered: