You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RPM and PKG packages include a short descriptor for the license, but after #1812 Briefcase will no longer know that (it either has a licence file or a licence text which may or may not be a short descriptor). Consequently, it is always set to "Unknown".
Prior to #1812 briefcase might have a way to know the license descriptor, but it is no guarantee that it matches the LICENSE file.
Steps to reproduce
Build an RPM or PKG bundle
Look at the spec file
Observe that the "License" field is set to "Unknown"
Expected behavior
A short license descriptor is included in the RPM spec file and the PKGBUILD-file
Screenshots
No response
Environment
Any environment
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
As a suggested fix: when the license configuration item is parsed, it should be parsed into a License object that has properties for the different forms that the license can take - the path on disk, the literal text of the license, a short descriptor of the license (in SPDX format, plus PyPA-compatible format). It should be possible to construct the License instance from any of the legal input types that PEP621 allows.
Describe the bug
RPM and PKG packages include a short descriptor for the license, but after #1812 Briefcase will no longer know that (it either has a licence file or a licence text which may or may not be a short descriptor). Consequently, it is always set to "Unknown".
Prior to #1812 briefcase might have a way to know the license descriptor, but it is no guarantee that it matches the LICENSE file.
Steps to reproduce
Expected behavior
A short license descriptor is included in the RPM spec file and the PKGBUILD-file
Screenshots
No response
Environment
Any environment
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: