`libgit2`的实际policy是GPLv2 + linking exception

[npc1054657282]

你在什么场景下需要该功能？

libgit2表面上是GPLv2，但是其协议内部实际上包含了“linking exception”，即明确豁免在未修改libgit2本身时，静态或者动态链接时的许可传染性。
协议有类似linking exception的库并不止一个。
这会导致添加此类包时，对它们的链接实际上不违反政策，但是依然会被报告违反了GPLv2协议。为了少数包的问题加入set_policy("check.target_package_licenses", false)让人感觉并不优雅

描述可能的解决方案

可能的解决方案1：针对此类情景专门添加对应的GPL-2.0-linkging-exception政策。
可能的解决方案2：为所有政策添加可能的exception参数
可能的解决方案3：对于存在此类问题的包，直接删除set_policy相关内容

描述你认为的候选方案

No response

其他信息

No response

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Title: = The actual policy of libgit2 is GPLv2 + linking exception

In what scenario do you need this function?

libgit2 is on the surface GPLv2, but its protocol actually contains a "linking exception", which means that it explicitly exempts the contagiousness of licensing when static or dynamic links without modifying libgit2 itself.
There is more than one library similar to linking exception in the protocol.
This results in the fact that linking to such packages does not actually violate the policy when adding them, but will still be reported to violate the GPLv2 protocol. Adding set_policy("check.target_package_licenses", false) to a few packages is not elegant

###Describe possible solutions

Possible solution 1: Add the corresponding GPL-2.0-linking-exception policy specifically for this scenario.
Possible Solution 2: Add possible exception parameters to all policies
Possible solution 3: For packages with such problems, directly delete the set_policy related content

Describe what you consider to be a candidate

No response

Other information

No response