You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At 1.x, files created by .NET Core had the execute bit set.
This means that NuGet packages containing executables would work, independent of the bit being set in the zip file.
For 2.x, the execute permission is no longer set. (dotnet/coreclr#7995)
This means NuGet packages need to be created and unpacked with correct permissions.
This is not the case currently.
Most packages contain only dlls and so files, they seem to work fine without the x-bit.
Packages containing executables&scripts are affected.
Once the packing is made permission aware, packages that rely on the 1.x behavior to set the x-bit will need to be repacked for 2.0.
The text was updated successfully, but these errors were encountered:
At 1.x, files created by .NET Core had the execute bit set.
This means that NuGet packages containing executables would work, independent of the bit being set in the zip file.
For 2.x, the execute permission is no longer set. (dotnet/coreclr#7995)
This means NuGet packages need to be created and unpacked with correct permissions.
This is not the case currently.
Most packages contain only dlls and so files, they seem to work fine without the x-bit.
Packages containing executables&scripts are affected.
Once the packing is made permission aware, packages that rely on the 1.x behavior to set the x-bit will need to be repacked for 2.0.
The text was updated successfully, but these errors were encountered: