Re: copyright precision
On Aug 15 2016, Simon McVittie <email@example.com> wrote:
> On Mon, 15 Aug 2016 at 18:17:52 +0200, Stefano Zacchiroli wrote:
>> The problem we're having here is clearly about *tooling*. If we had a
>> good toolchain to compile and audit machine-readable debian/copyright
>> files without sweating, nobody would complain.
> I have three slightly devil's-advocate responses to that:
> * If we had a good toolchain to compile and audit this stuff, people
> and companies who want to know the copyright holders could just use
> that to inspect the upstream source code and cut out the middle-man.
I think even the best tooling wouldn't be able to automatically generate
correct copyright files. However, it would make it feasible to keep an
initially-correct copyright file correct over time (by flagging
potentially copyright affecting changes in an upstream release and
providing a straightfoward way to integrate those changes).
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«