-
Notifications
You must be signed in to change notification settings - Fork 174
Support having spaces in OfficialBuilder #677
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
Conversation
I am not sure what the code flow looks like these days. Please let me know if I should open PRs against the individual component repos instead. |
The change to build.sh should only be made in the arcade repo. This is because it's within the eng/common directory. Edits within that directory should only be made in arcade and dependency flow will flow those changes to all the other repos, including the VMR. |
By arcade repo, I mean https://github.com/dotnet/arcade, not the src/arcade directory in the VMR. |
Sorry, @mthalman that I have to disagree here. We have a different policy:
Based on that, @omajid please revert all the eng/common changes except for the one under src/arcade. ... and yes, we should document this. Also see https://github.com/dotnet/dotnet?tab=readme-ov-file#where-to-make-changes |
FYI - dotnet/source-build#5185 will help prevent changes to eng/common. |
869d8a1
to
24322a7
Compare
Thanks, @mthalman and @ViktorHofer ! I have reverted all eng/common changes except to src/arcade/eng/common. However, that means that building with |
Currently, running the following command fails: $ ./build.sh --prep --source-build /p:OfficialBuilder='Red Hat' Lots of scripts and projects assume that there are no spaces in OfficialBuilder (and other properties). Having spaces breaks in all sorts of places. This is a minimal fix to try and resolve that. The primary change is to use bash arrays to store values (properties and arguments) to make sure they are quoted correctly when passed to other places.
24322a7
to
b76efe1
Compare
That's correct. |
Yes. If we have a passing build tonight, I can do another re-bootstrap tomorrow. I want one for other reasons as well. |
Currently, running the following command fails:
Lots of scripts and projects assume that there are no spaces in OfficialBuilder (and other properties). Having spaces breaks in all sorts of places. This is a minimal fix to try and resolve that.
The primary change is to use bash arrays to store values (properties and arguments) to make sure they are quoted correctly when passed to other places.