On Mon, Oct 13, 2014 at 1:14 PM, sebb <seb...@gmail.com> wrote: > >>> 4. presence or absence of NOTICEs in source distribution doesn't > >>> affect binary distribution. > >> > >> Not true. > > > > Ditto. > > If you are saying that the NOTICE in an ASF binary release has no > direct bearing on the NOTICE in the corresponding ASF source release, > then strictly speaking I agree with you (though of course both will > have the same pre-amble, and may indeed be identical). The NOTICE in > an ASF source release does however affect the corresponding ASF binary > release. > > However, if you are saying that a NOTICE in an arbitrary _binary_ > distribution does not affect an ASF _source_ distribution which > includes said _binary_ distribution, then I don't agree. Likewise if > you swap _binary_ and _source_ in the previous sentence.
I think that the simpler form of the assertion is just that the contents of the NOTICE depends on the content of the distribution, be it source, binary or Martian cookies. It is reasonably common for the source artifacts to include upstream artifacts that are not necessarily easily or stably available and not to include many runtime dependencies. This will increase or decrease the content of the NOTICE and LICENSE files. Conversely, it is common for binary artifacts to include upstream binary artifacts for conveniences and to not include test artifacts. A single binary artifact may be for a limited purpose, thus shrinking the scope of NOTICE and LICENSE relative to the corresponding source artifact. All of these are simpler if you simply look at the bits in the artifact and declare them appropriately.
