Bug#1100386: licensecheck should [optionally] output SPDX-compliant license identifiers.

2025-03-26 Thread Dom Rodriguez
On 26.03.2025 00:26, Dom Rodriguez wrote: I'll close this for now, as those other bug reports seem to - partially, one way or another - cover the -only/-or-later bits we need. Actually, looking at the Debbugs system, which I'm not /too/ familiar with - is there a way to close th

Bug#1100386: licensecheck should [optionally] output SPDX-compliant license identifiers.

2025-03-26 Thread Dom Rodriguez
On 13.03.2025 15:29, Jonas Smedegaard wrote: Quoting Dom Rodriguez (2025-03-13 14:48:21) On 13.03.2025 11:01, Jonas Smedegaard wrote: >Quoting Dom Rodriguez (2025-03-13 01:18:03) >> It would be useful for `licensecheck` to output SPDX-compliant license >> identifiers, so that it

Bug#1100386: licensecheck should [optionally] output SPDX-compliant license identifiers.

2025-03-13 Thread Dom Rodriguez
Hi Jonas, On 13.03.2025 11:01, Jonas Smedegaard wrote: Hi Dom, Quoting Dom Rodriguez (2025-03-13 01:18:03) It would be useful for `licensecheck` to output SPDX-compliant license identifiers, so that it can be used in SPDX/CycloneDX SBOMs. Do you mean like this?: ``` licensecheck

Bug#1100386: licensecheck should [optionally] output SPDX-compliant license identifiers.

2025-03-13 Thread Dom Rodriguez
output mode could be done in a Unix-style pipe from the [default] tabular output in a pipeline processing mode? Happy to do some experimenting with the above approach, but also keen for other suggestions. Best regards, -- Dom Rodriguez (he/him) Software Engineer Codethink Ltd Codethink delivers