From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-11-04 11:09:50
On Saturday 04 November 2006 19:04, Thomas Witt wrote:
> Vladimir Prus wrote:
> > On Friday 03 November 2006 22:14, Rene Rivera wrote:
> >> Thomas Witt wrote:
> >>> This is a repost of an earlier message with a slightly more alarming
> >>> (at least I hope so) subject.
> >>> Hi,
> >>> A large number of files (~400) in the build system are missing licenses
> >>> and copyright. See the inspection report on the developer list for
> >>> details. What are we going to do about it?
> >>> THIS HAS TO BE RESOLVED BEFORE 1.34.0 GOES OUT THE DOOR!
> >> I guess we need some one to go through and do all the edits.
> > Well, given that most of them files existed in 1.33 I'm not sure I see
> > the urgency of fixing them now ;-) It least I surely did not wrote 400
> > files in last year.
> IIRC we decided a long time ago that this issue is important to some of
> our users and thus has to be addressed. That said another reason for the
> urgency is that large numbers of failures make the inspection reports
> useless, nobody will care. I would like to change that and therefor the
This latter issue can be solved by making the inspection tool ignore all build
> I would be really thankful if this could be fixed.
It would be great if somebody wrote a script to automatically update the
license ;-) I probably can do it myself, but first need to fix more important
issues -- namely the differences in the set of variants built with V1 and V2.
> >> I think
> >> Volodya wrote most of those files. Volodya is it OK to go through and
> >> have someone add those?
> > Yes, sure. And I'm in the blanket permission file anyway.
> >> We wouldn't want to mess with any pending
> >> changes you have.
> >> Also the remaining BBv1 files are from authors without a blanket
> >> permission on file. So it would take reminding the authors to add the
> >> info.
> It was my understanding that we don't ship BBv1 with 1.34.0, but I might
> very well be wrong what's the plan?
I think the plan was to retain V1 for at least one release cycle.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk