Skip to content

Spectre.Console repo fixes #248

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

Merged
merged 6 commits into from
Jan 4, 2024
Merged

Spectre.Console repo fixes #248

merged 6 commits into from
Jan 4, 2024

Conversation

mthalman
Copy link
Member

@mthalman mthalman commented Jan 3, 2024

Fixes dotnet/source-build#3817

Because spectre.console has a global.json file targeting 8.0.100, it fails to build now that the tooling for the SBE has been updated to use .NET 9 SDK.

This is fixed by using the existing UpdateGlobalJsonVersions target. The problem is that it makes use of an MSBuild task that doesn't exist in the repo. So I've added it back along with implementation which will build the tasks project.

@mthalman mthalman requested review from baronfel and MichaelSimons and removed request for MichaelSimons January 3, 2024 22:24
@@ -1,86 +0,0 @@
-/*
-Ported from: https://rosettacode.org/wiki/Mandelbrot_set#C.23
-Licensed under GNU Free Documentation License 1.2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this actually address the license issue? The license will still exist in this patch.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But it wouldn't exist in the VMR.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would (see here) - these patches get applied dynamically to the inner build of source-build-externals. They are treated differently than the source-build patches.

@@ -0,0 +1,103 @@
From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think Patrik was going to remove this from the repo tonight, so if we stall a day we may just be able to update the submodule and remove this patch + remove my PackageReference-commenting patch.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, is a new release planned soon then?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a new release, but there have only been 9 commits to main since the 0.48.0 release was tagged (at time of writing), and the majority of those have been build-infra related, so I could see an argument for us bumping the submodule to the commits from today that introduced the PackageReference Condition and removed the incompatibly-licensed example file.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our preference is to only pin to a release commit to ensure quality as established by the repo maintainer.

@mthalman
Copy link
Member Author

mthalman commented Jan 4, 2024

I've removed the Mandelbrot deletion patch since the path still includes a reference to the license. There doesn't appear to be a way to define a patch that doesn't include the file's content. So we'll need to address this via VMR cloaking.

@mthalman mthalman requested a review from MichaelSimons January 4, 2024 15:27

<ItemGroup>
<PackageReference Include="Microsoft.Build">
<Version>15.7.179</Version>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to encapsulate this version in versions.props? It would make updating easier and follow the arcade patterns.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll log a separate issue for that since it should be done for all the other relevant external repos as well.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

spectre.console repo fails to build in SBE
3 participants