reuse-tool
reuse-tool copied to clipboard
fsfe
reuse is a tool for compliance with the REUSE recommendations.
Out of a sudden we start getting error with Python 3.6.15, running `reuse` in a [GitHub action](https://github.com/oss-review-toolkit/ort/runs/3929484553?check_suite_focus=true): ``` Collecting reuse Downloading reuse-0.13.0-py3-none-any.whl (140 kB) Collecting binaryornot Downloading binaryornot-0.4.4-py2.py3-none-any.whl (9.0 kB)...
The default file headers look like this: ``` // © 2022 Vlad-Stefan Harbuz // // SPDX-License-Identifier: license-goes-here ``` However, I would prefer to do without the middle line. I understand...
The debian pypi redirector [1] detects a gpg key used for signing releases. It would be easier to verify those if the project published a gpg keyring with keys that...
"Copyright" is English-specific, while the copyright symbol can be difficult to type. These are good reasons to use `(C)` or `(c)`, and I've seen many projects use these. This pull...
For example, we had the entry like ``` Files: pkgcfg/*.pc.acr Copyright: ... License: ... ``` and a `reuse lint` action on every commit. But when whole `pkgcfg/` directory was removed,...
Hi! Thanks for the great tool! I have a feature request that would greatly improve my current workflow with `reuse-tool`, that includes a step in my [pre-commit hooks](https://pre-commit.com/) that calls...
### Steps to reproduce Create a new reuse project under git. Add a git submodule which is compliant with the reuse specification, but covers some files with debian's dep5 mechanism....
During the implementation of the REUSE.software standard, I added the licensing and copyright information to testdata files through dep5. However, reuse tool still shows missing/bad licensing information from testdata files....
For some reason this wasn't working for me, and black started formatting everything in `.tox`. Removing this config fixed it.
The VHDL comment style is "--", recently others are supported but still a lot of code uses "--" for comments
