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
LicenseRef-Proprietary or LicenseRef-proprietary? #309
Comments
|
If it helps, fwupd and the LVFS uses |
|
Interesting. SPDX itself says The odd situation we have here is that we kind of need to diverge from the current SPDX specification a bit, as we can't use their recommendation for specifying external license texts (that was added after AppStream already supported a different syntax).
Would that make sense to you? Note that |
|
Actually, it looks like AppStream already implements this this way, and does ignore case-sensitivity of |
As per discussion on ximion#309, it should be `LicenseRef-proprietary`, rather than `LicenseRef-Proprietary`. Signed-off-by: Philip Withnall <pwithnall@endlessos.org> Fixes: ximion#309
As per discussion on ximion#309, it should be `LicenseRef-proprietary`, rather than `LicenseRef-Proprietary`. Signed-off-by: Philip Withnall <pwithnall@endlessos.org> Helps: ximion#309
|
I’ve opened #310 to make the casing consistent in the spec, which should fix the immediate issue. I don’t plan to work on any further cleanups, additional examples, clarifications, etc. in the spec or libappstream code. |
|
I don't expect anyone to work on anything unless they explicitly stated so. |
|
With this being explicitly mentioned in the spec now, and GNOME Software using |
The specification uses different case in its prose and examples, for the
LicenseRef-[pP]roprietarytag.Which is correct?
See also: https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1161
The text was updated successfully, but these errors were encountered: