Re: Making copyright holders easier to parse

From: pbristow_at_[hidden]
Date: 2019-07-29 08:50:33

> -----Original Message-----
> From: Boost <boost-bounces_at_[hidden]> On Behalf Of Paul A Bristow via
> Boost
> Sent: 27 July 2019 10:14
> To: boost_at_[hidden]
> Cc: pbristow_at_[hidden]
> Subject: Re: [boost] Making copyright holders easier to parse
> 
> > -----Original Message-----
> > From: Boost <boost-bounces_at_[hidden]> On Behalf Of Antony
> > Polukhin via Boost
> > Sent: 27 July 2019 05:46
> > To: boost_at_[hidden] List <boost_at_[hidden]>
> > Cc: Antony Polukhin <antoshkka_at_[hidden]>
> > Subject: Re: [boost] Making copyright holders easier to parse
> >
> > On Sat, Jul 27, 2019, 04:44 Giovanni Mascellani via Boost <
> > boost_at_[hidden]> wrote:
> > <...>
> >
> > > My question is: are you interested in this kind of patches? Of
> > > course I would still go through the ordinary patch submission
> > > procedure. I am just asking if this kind of patches would be well received or
> not.

I have another suggestion.

We already have the inspect program written in C++ which 'parses' and emits an html report on missing copyright (and many other transgressions of Boot guidelines).

See https://www.boost.org/doc/libs/release/tools/inspect/inspect.cpp

and copyright_check.cpp and .hpp

I suspect that this could easily be altered to add an output to a file of copyright authors(s) and date(s) in whatever format and file type is easiest  for Debian to deal with.

For example a test file containing
Library_name
Author(s)_name  Copyright_Date(s)
...

The build tools are in

I:\boost\tools\inspect

If this works, I feel we could use this updated version in Boost itself.  Other packagers and those needing to jump through copyright and GDPR hoops might find helpful.

This would avoid a paroxysm in our extensive CI system 😊

Paul

Paul A. Bristow
Prizet Farmhouse
Kendal, Cumbria 
LA8 8AB           UK