[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: PostGIS 2.1.4



On 09/25/2014 04:32 PM, Markus Wanner wrote:
> On 09/25/2014 04:21 PM, Sebastiaan Couwenberg wrote:
>> We can use some more wildcards, but we also need a lot of separate license
>> specifications for individual files.
>>
>> For doc/* CC-BY-SA-3.0 should be used, but there are some differently
>> licensed files under the doc directory (mostly Makefile templates).
>>
>> The autotools script have different authors, copyright years and licenses,
>> requiring a lot of extra license specifications.
>>
>> There has been some debate about what to document in the copyright file
>> triggered by the recently introduced lintian checks for dep5, that was
>> mostly about generated files from autotools.
>>
>> The relevant documentation is:
>>
>> https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#copyright-field
>>
>> And the related policy sections:
>>
>> https://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgcopyright
>> https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
>> https://www.debian.org/doc/debian-policy/ch-archive.html#s-pkgcopyright
>>
>> The policy doesn't specify much other that that the verbatim copyright and
>> license needs to be included.
>>
>> The copyright-format specifiction says:
>>
>> "The Copyright field collects all relevant copyright notices for the files
>> of this paragraph. Not all copyright notices may apply to every individual
>> file, and years of publication for one copyright holder may be gathered
>> together. For example, if file A has:"
>>
>> So it's possible to more group files with the same license even if the
>> copyright is not identical between the files.
> 
> Thanks for all these pointers. I'll dig through those later today.
> 
> I understood you're currently working on it? Please feel free to push to
> the git repo.

I've completed the review of the all the files lintian complained about,
and updated the copyright file accordingly.

The package is good to go now I'd say.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/E88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1


Reply to: