Re: Unaddressed use cases for machine-readable debian/copyright files

2017-04-07 Thread Dominique Dumont
On Saturday, 25 March 2017 16:25:38 CEST Guillem Jover wrote: > Personally I have no issue with coalescing > copyright notices, as long as they are all for the same license, etc. > I even coalesce copyright years for the same owner. Coalescing copyright notices and years is also done when running

Re: Unaddressed use cases for machine-readable debian/copyright files

2017-03-25 Thread G. Branden Robinson
On Sat, Mar 25, 2017 at 04:25:38PM +0100, Guillem Jover wrote: > Hi! Thanks for your feedback! Been a while since we've chatted. :) > On Fri, 2017-03-24 at 14:02:49 -0400, G. Branden Robinson wrote: > > In returning my attention to current Debian packaging practices and > > conventions I took m

Re: Unaddressed use cases for machine-readable debian/copyright files

2017-03-25 Thread Russ Allbery
Guillem Jover writes: > Something that is also a common source of confusion, is that because > it specifies a Files field, it seems it compels people to do very > fine-grained splitting. Personally I have no issue with coalescing > copyright notices, as long as they are all for the same license,

Re: Unaddressed use cases for machine-readable debian/copyright files

2017-03-25 Thread Guillem Jover
Hi! On Fri, 2017-03-24 at 14:02:49 -0400, G. Branden Robinson wrote: > In returning my attention to current Debian packaging practices and > conventions I took my first serious look at good old DEP5, and brought > the debian/copyright file for my first-ever package, xtrs[1], into > conformance wit

Unaddressed use cases for machine-readable debian/copyright files

2017-03-24 Thread G. Branden Robinson
Hi folks, Sorry to bother you again so soon. In returning my attention to current Debian packaging practices and conventions I took my first serious look at good old DEP5, and brought the debian/copyright file for my first-ever package, xtrs[1], into conformance with the new[2] standard[3]. Howe