-
Notifications
You must be signed in to change notification settings - Fork 5k
The official build doesn't produce Crossgen2 pack RPM or Debian packages #1985
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
Comments
I think it's because of this line:
The Debian package production step runs as I think a simple fix would be to add I'm going to try using a target to manipulate the process instead, and have it condition based on |
Does it mean that I need to be an admin to install crossgen2? I though that crossgen2 is going to be a nuget package, and you will acquire it by adding a nuget package reference somewhere. |
It's both, the We may decide not to include the crossgen2 pack in any SDK installation method, like runtime packs. Didn't actually consider that before... I don't object to doing a little work now to keep it unblocked though. |
I think the only packaging for crossgen2 we need to worry about is nuget. .msi/.rpm./.deb does not matter for foreseeable future or ever. |
Ok, thanks. It makes sense to me for this to be similar to the runtime packs in that way. I'll go ahead and close and note that on #1867. |
The official build produces e.g.
dotnet-crossgen2-pack-5.0.0-alpha.1.20071.1-win-x64.msi
, but no correspondingdotnet-crossgen2-pack-5.0.0-alpha.1.20071.1-win-x64.rpm
or.deb
for use on Linux. These are required for the SDK to incorporate them properly--I think not having them will make it harder to integrate SDK support.I'm taking a look, I would expect these to be created.
/cc @fadimounir @dotnet/crossgen-contrib
The text was updated successfully, but these errors were encountered: