> Including Category B binaries in a source release is mentioned in ASF policy
> here [1].
Sorry to keep banging the same drum, but I read this before our earlier emails,
and if this is the intended meaning it needs to be rewritten. I also doubt this
was the intended meaning of the original author. The subject of the bracketed
clause is grammatically ambiguous, so other contextual cues must be used to
interpret it:
> BINARY-ONLY INCLUSION CONDITION
> Unless otherwise specified, all Category B licensed works should be included
> in binary-only form in Apache Software Foundation convenience binaries (and
> not source code).
1. Source _code_ cannot (pretty much by definition) contain any binaries, so
the only semantically plausible interpretation is prohibiting the inclusion of
the dependency's source code in the release
2. The heading "binary-only inclusion" provides the motivating context for the
sentence, strongly suggesting the bracket is likely a clarifying reiteration
that the dependency's source code should not be included
3. Elsewhere in this document source code appears to refer to the normal
meaning, i.e. source code, not source packages/releases
Since we as a community use these websites to determine our correct actions,
I'm not sure we can really help fix this with PRs, since we have no independent
primary knowledge of the desired content. I still don't really know for sure
the source of your expectation.
I'm sure we can update our build scripts to fetch these libraries instead of
bundling them, if we can get some kind of official confirmation that this is
indeed necessary. Finding people willing to volunteer to go back and modify
earlier releases may be a tall order, however.
On 27/03/2021, 23:24, "Justin Mclean" <jmcl...@apache.org> wrote:
Hi,
> This is a known problem. Please help out.
That is the reason of having those jars in the source release? Could it
just be replaced by a series of curl commands in a shell script?
I can help fix up the LICENSE and NOTICE files, but the inclusion of
compiled code in a source release is the bigger is here.
> It has been made mention of on most of the recent vote release threads,
and
> we have a ticket CASSANDRA-16391 open to deal with it (eta is immediately
> after 4.0).
I'm not sure that fixing this after a 4.0 release would be an option and
the question may come up of what needs to be done with the source releases that
are already public.
Including Category B binaries in a source release is mentioned in ASF
policy here [1].
Thanks,
Justin
1. https://apache.org/legal/resolved.html#binary-only-inclusion-condition
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
