Open dmorn opened 4 years ago
reuse 0.5.2
This version is outdated. Can you try with a newer version? Newer versions of reuse should—by default—completely ignore submodules unless you do reuse --include-submodules lint
. In which case it might still not recognise nested .reuse
folders, but I'm not sure.
Hi @carmenbianca (I notice now I heard you speaking at the SFScon! 😊), yes you'r right: I updated the tool, now I'm running version 0.8.0
, and it does not check submodules. --include-submodules
fails as above though.
I am running latest git version of reuse as of today (exactly v1.0.0
),
and it does check git submodules again, and in my case fails because of this.
What would we want to happen, optimally?
.reuse/dep5
, instead of just in the project-/scan-root?.reuse/dep5
exists for each git sub-module?I am not sure it would be good to use (my feeling is rather, not so much, as it would be too manual/work intensive), but as it seems not to exist, I would say it makes little sense that we go deeper into it.
What I mean is something similar like you have in programming languages, like import
in python, or #include
in C/C++.
Not sure on the status of this, but going back to the original posters problem. Given a sub-directory that is reuse compliant it would be useful if when running the reuse tools on a parent project for the license information be properly propagated up. This would seem to me to be a common use case where for example a large project has dependencies on several other projects. In an ideal world those dependencies would also be using reuse and developers of the parent project should only need to declare license information for their own files.
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. If you run the linter on the parent directory (not the submodule), it will complain that the submodule is not reuse complaint.
Example
Let's create an empty git repo first, add the submodule and check its complaincy:
Now make a step back and check from the parent git repo.
Hint
I'm not a python fan and I did not dig into the code, but it looks like
reuse
is not taking into consideration nested.reuse
folders.Context
OS:
Darwin jecoz.local 19.2.0 Darwin Kernel Version 19.2.0: Sat Nov 9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64 x86_64
reuse version:reuse 0.5.2