[PR #36] [MERGED] Debian: Specify the .NET Core dependencies for Debian in the .targets file #182

New Issue

claunia · 2026-01-29T16:31:04Z

claunia commented

2026-01-29 16:31:04 +00:00

📋 Pull Request Information

Original PR: https://github.com/quamotion/dotnet-packaging/pull/36
Author: @qmfrederik
Created: 10/16/2017
Status: ✅ Merged
Merged: 10/16/2017
Merged by: @qmfrederik

Base: master ← Head: fixes/deb-versions

📝 Commits (2)

aa08e70 Specify the .NET dependencies in the .targets file instead of code, and let the user override.
d7e15ed Treat package dependencies as strings

📊 Changes

5 files changed (+41 additions, -58 deletions)

View changed files

📝 Packaging.Targets/Deb/DebPackageCreator.cs (+3 -6)
➖ Packaging.Targets/Deb/PackageDependency.cs (+0 -31)
➖ Packaging.Targets/Deb/PackageDependencyRelation.cs (+0 -11)
📝 Packaging.Targets/DebTask.cs (+20 -9)
📝 Packaging.Targets/build/Packaging.Targets.targets (+18 -1)

📄 Description

Instead of hard-coding the dependencies required by .NET Core, specify them in the Packaging.Targets.targets file in an ItemGroup named DebDotNetDependencies, and flow those values to the DebPackageCreator via the DebTask.

If, for some reason, the version of the packages we select by default are not OK for an end-user, they can override this value by manually creating a DebDotNetDependencies ItemGroup. In that case, we'll use whatever value the user specified.

Fixes #35

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/quamotion/dotnet-packaging/pull/36 **Author:** [@qmfrederik](https://github.com/qmfrederik) **Created:** 10/16/2017 **Status:** ✅ Merged **Merged:** 10/16/2017 **Merged by:** [@qmfrederik](https://github.com/qmfrederik) **Base:** `master` ← **Head:** `fixes/deb-versions` --- ### 📝 Commits (2) - [`aa08e70`](https://github.com/quamotion/dotnet-packaging/commit/aa08e706a2b05eed748e1bbb3c444f3730e74f4f) Specify the .NET dependencies in the .targets file instead of code, and let the user override. - [`d7e15ed`](https://github.com/quamotion/dotnet-packaging/commit/d7e15ed4ff234a324b782d44a1293ad89f3cce4d) Treat package dependencies as strings ### 📊 Changes **5 files changed** (+41 additions, -58 deletions) <details> <summary>View changed files</summary> 📝 `Packaging.Targets/Deb/DebPackageCreator.cs` (+3 -6) ➖ `Packaging.Targets/Deb/PackageDependency.cs` (+0 -31) ➖ `Packaging.Targets/Deb/PackageDependencyRelation.cs` (+0 -11) 📝 `Packaging.Targets/DebTask.cs` (+20 -9) 📝 `Packaging.Targets/build/Packaging.Targets.targets` (+18 -1) </details> ### 📄 Description Instead of hard-coding the dependencies required by .NET Core, specify them in the `Packaging.Targets.targets` file in an `ItemGroup` named `DebDotNetDependencies`, and flow those values to the `DebPackageCreator` via the `DebTask`. If, for some reason, the version of the packages we select by default are not OK for an end-user, they can override this value by manually creating a `DebDotNetDependencies` ItemGroup. In that case, we'll use whatever value the user specified. Fixes #35 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

claunia added the pull-request label 2026-01-29 16:31:04 +00:00

claunia closed this issue

2026-01-29 16:31:04 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dotnet-packaging#182