I have noticed some packages using the newer machine-readable copyright format, but not specifying any copyright for debian/*That's not good practice. You should ask the package maintainer to include
What does that mean about the copyright status of debian/* ? If I wantIf the copyright file doesn't specify the license, and there are no comments in the files specifying the license, then the maintainer of that package really should fix that. That leaves the license ambiguous and you may not make any assumptions about your use of the file.
to re-use a file therein in another package, can I do so?
I have noticed some packages using the newer machine-readable copyright format, but not specifying any copyright for debian/*
Le 02/01/2021 à 11:30, Matthew Vernon a écrit :
I have noticed some packages using the newer machine-readable
copyright format, but not specifying any copyright for debian/*
FWIW, I do that in most of the (simple) packages I’m maintaining: I’m fine using the same license as upstream, hence the “Files: *” catch
the correct license also for debian/*.
The debian/ directory in those packages may have very little
copyrightable content anyway (not sure a trivial override in d/rules
or data in d/u/metadata would eligible for example). The only
creativity is often limited to the package description, that is
directly copied (or adapted) from upstream, or a patch cherry-picked
(or forwarded) upstream, where I’m not even the copyright owner
(upstream is, so again, “Files: *” catches the correct information).
On Saturday, January 2, 2021 10:30:56 AM EST Matthew Vernon wrote:
I have noticed some packages using the newer machine-readable copyright format, but not specifying any copyright for debian/*That's not good practice. You should ask the package maintainer to include such information in debian/copyright. They would know the history best. Be sure to check for a wildcard though, like
Files: *
as that could apply to debian/.
What does that mean about the copyright status of debian/* ? If I wantIf the copyright file doesn't specify the license, and there are no comments in
to re-use a file therein in another package, can I do so?
the files specifying the license, then the maintainer of that package really should fix that. That leaves the license ambiguous and you may not make any assumptions about your use of the file.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 18:06:52 |
Calls: | 6,646 |
Calls today: | 1 |
Files: | 12,190 |
Messages: | 5,327,231 |