Skip to content
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

Automatically add dotnet6-internal feeds #7580

Merged
merged 1 commit into from
Jul 2, 2021

Conversation

mmitche
Copy link
Member

@mmitche mmitche commented Jun 30, 2021

If dotnet6 is present, add dotnet6-internal and dotnet6-internal-transport.
This is the same methodology as .NET 5 and .NET 3.1

To double check:

If dotnet6 is present, add dotnet6-internal and dotnet6-internal-transport.
This is the same methodology as .NET 5 and .NET 3.1
@mmitche mmitche requested a review from lukas-lansky June 30, 2021 21:19
@@ -129,6 +129,30 @@ if [ "$?" == "0" ]; then
PackageSources+=('dotnet5-internal-transport')
fi

# Ensure dotnet6-internal and dotnet6-internal-transport are in the packageSources if the public dotnet6 feeds are present
Copy link
Contributor

Choose a reason for hiding this comment

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

It might be nice to loop over ("dotnet3.1-internal" "dotnet5-internal" "dotnet6-internal") here to get rid off the almost-duplicated code.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah...I just didn't want to mess with it too much. Also the URIs for 3.1 are different than 5.0 and 6.0

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.

2 participants