On Jun 3, 2008, at 11:45 PM, Bertrand Delacretaz wrote:
On Wed, Jun 4, 2008 at 12:35 AM, Roy T. Fielding
<[EMAIL PROTECTED]> wrote:
...I'd rather have a set of hand-edited NOTICE files that accurately
reflect each of the release packages....
I see your point, and thanks for your changes in etc/notice/notices,
that will help a lot.
The nice thing (IMHO) about generating the notices from the Maven
dependencies, is that this will expose any new dependencies that might
have been added next time we do a release, without having to manually
check our 55 notice files by hand.
But I agree about refining the process with exceptions, I'll modify
the mknotice script now, to ignore #comment lines.
But the NOTICE files are not for describing build dependencies.
They exist to satisfy the copyright license of packaged distributions.
If the notices aren't required by the bits in the package, then they
don't
belong in NOTICE. That means there will be a different NOTICE file
required
for each differently packaged set of bits. We must do this by hand.
I think that tracking detailed dependencies and all of their licenses
is very useful and necessary for helping us construct the subsets
that need to be noted in LICENSE (the union of all licenses) and NOTICE
(the union of a required notices) and README (everything else).
....Roy
