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
We would like to also include SPDX-FileType and SPDX-FileName. The usefulness of these tags is still being debated, and we might drop them altogether. It can be argued that SPDX-FileName is largely irrelevant, but we would like to use it to canonicalize the full path and file name relative to the project root. To do this, it seems that we can add both to a Jinja template.
For SPDX-FileName, we would need a way to dynamically determine the file name for each file being processed. A variable to represent the current file could help.
For SPDX-FileType, we would seemingly need to use a conditional based on the path. E.g. {% if "/bin" in path %}SPDX-FileType: BINARY{% endif %}
Is this possible or out-of-scope?
For now we are including the information in REUSE.toml, which is silently ignored:
reuse-tool already supports
SPDX-FileCopyrightText
andSPDX-FileContributor
as defined in https://spdx.github.io/spdx-spec/v2.3/file-tags/.We would like to also include
SPDX-FileType
andSPDX-FileName
. The usefulness of these tags is still being debated, and we might drop them altogether. It can be argued that SPDX-FileName is largely irrelevant, but we would like to use it to canonicalize the full path and file name relative to the project root. To do this, it seems that we can add both to a Jinja template.{% if "/bin" in path %}SPDX-FileType: BINARY{% endif %}
Is this possible or out-of-scope?
For now we are including the information in REUSE.toml, which is silently ignored:
The text was updated successfully, but these errors were encountered: