Open
Description
Details about Problem
NuGet product used (NuGet.exe | Visual Studio | MSBuild.exe | dotnet.exe): nuget.exe CLI via Mono
Product version: 5.8.0.6930
Worked before? If so, with which NuGet version: No
Operating Systems: Linux and macOS
We create nuget packages on Linux and macOS by ‘nuget.exe pack ..’. Our source folder contains libraries and the set of symbolic links following Linux Shared Library Versioning Guidelines that we expect to be included into nuget package archive as symbolic links. But during packaging, the nuget.exe tool converts the symbolic links into files, which leads to 3x package size increase. As a result, some packages exceed 250Mb limit and cannot be deployed to Nuget gallery. Please fix the nuget.exe tool to support symbolic links.
Activity
nkolev92 commentedon Apr 14, 2021
Hey @DanVev,
I was able to repro the behavior on Windows, so it's consistent. As such I've retitle the issue to make it clear it's a feature ask.
While package size is a concern, we'd need to consider how older clients may work with these new packages.
JonDouglas commentedon Apr 16, 2021
This might be dependent on dotnet/runtime#24271
nkolev92 commentedon Apr 19, 2021
This is not high on our priority list right now.
If we were to ever to this, we'd need to make sure that the sym links don't point outside of the package.
44 remaining items