RPM generation doesn't support LinuxPath in combimation with Link attributes #37

Closed
opened 2026-01-29 16:27:47 +00:00 by claunia · 1 comment
Owner

Originally created by @daniel-sherwood on GitHub (Sep 6, 2018).

MSBuild supports using the Link attribute to reference a file in a particular location in the project, build or publish tree. If this is used in conjunction with the LinuxPath attribute, the file is not copied to the correct location.

The attached patch fixes this.
patch.txt

Originally created by @daniel-sherwood on GitHub (Sep 6, 2018). MSBuild supports using the Link attribute to reference a file in a particular location in the project, build or publish tree. If this is used in conjunction with the LinuxPath attribute, the file is not copied to the correct location. The attached patch fixes this. [patch.txt](https://github.com/qmfrederik/dotnet-packaging/files/2357835/patch.txt)
Author
Owner

@qmfrederik commented on GitHub (Sep 6, 2018):

Thanks! The patch looks good, but could you add a test for this? It could be as simple as adding an entry to the demo\cliscd\clisc.csproj file, and updating demo\cliscd\Tests.cs to include a test which makes sure the file has actually been deployed to the target.

@qmfrederik commented on GitHub (Sep 6, 2018): Thanks! The patch looks good, but could you add a test for this? It could be as simple as adding an entry to the `demo\cliscd\clisc.csproj` file, and updating `demo\cliscd\Tests.cs` to include a test which makes sure the file has actually been deployed to the target.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dotnet-packaging#37