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

Ensure correct path separator in nuspec files is used on different operating systems #502

Closed
ferventcoder opened this issue Dec 8, 2015 · 1 comment

Comments

@ferventcoder
Copy link
Member

If the nuspec contains a path separator specific to Windows ("\"(, non-Windows platforms are unable to find any files.

<files>
    <file src=""tools\**"" target=""tools"" />
  </files>

We need to fix NuGet to automatically switch the path separator from \ to / on non-Windows.

@ferventcoder
Copy link
Member Author

The workaround is that you can change it in the nuspec and it will work, but that is not fun for folks switching back and forth.

TheCakeIsNaOH added a commit to TheCakeIsNaOH/nuget-chocolatey that referenced this issue Jul 4, 2020
Converts the path separator character in the nuspec file source to the
character that is correct for the OS that is running the packing
operation. Changes "\" to "/" on Linux and MacOS systems, and
changes "/" to "\" on Windows systems.

Fixes: chocolatey/choco#502
@gep13 gep13 added this to the 0.10.16 milestone May 4, 2021
@gep13 gep13 added 4 - Done and removed 2 - Working labels May 4, 2021
@gep13 gep13 changed the title Convert path separator in nuspec files list on non-Windows Ensure correct path separator in nuspec files is used on different operating systems May 18, 2021
TheCakeIsNaOH added a commit to TheCakeIsNaOH/choco that referenced this issue Sep 29, 2021
Remove the "Building from Linux?" note from the built-in template nuspec.
Now that chocolatey#502 has been fixed, it is not longer relevant.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants