Yes, we need to bundle them in order to have a downloadable artifact that you can untar and start the service. Otherwise there's no way to have a binary distribution.
I'm going through the list of the flattened dependencies (Kind of the same exercise I did to compile the list for the incubator proposal). -- Matteo Merli <[email protected]> On Wed, Jul 12, 2017 at 10:53 AM, Joe F <[email protected]> wrote: > We will have to recursively analyze dependencies. Do we really have to > bundle the runtime dependency bits in the bin distribution? > > (quoting from http://www.apache.org/dev/licensing-howto.html) > > > a number of other "permissive" licenses which are approved > <http://www.apache.org/legal/resolved.html#category-a> for use by the ASF > Legal Affairs Committee. Some of these may require additions to NOTICE -- > if in doubt, ask > <http://www.apache.org/legal/resolved.html#asking-questions>. > > >If the dependency supplies a NOTICE file, its contents must be analyzed > and the relevant portions bubbled up into the top-level NOTICE file. > > >Dependencies of dependencies (including so-called "transitive > dependencies") are no different from first-order dependencies for the > purposes of assembling LICENSE and NOTICE: LICENSE and NOTICE need only be > modified to accommodate them *if and only if their bits are bundled*. > > Joe > > On Wed, Jul 12, 2017 at 10:39 AM, Matteo Merli <[email protected]> wrote: > > > Ok, I've been reading a bit of material, including : > > > > http://incubator.apache.org/guides/releasemanagement.html > > http://www.apache.org/dev/licensing-howto.html > > > > > > My current understanding is that we need to attach 2 different LICENSE > and > > NOTICE files to the source and binary artifacts that will be included in > > the release. > > > > So far, we have been releasing 2 artifacts : > > 1. pulsar-x.y-src.tar.gz --> All the sources (Java, C++, Python) > > 2. pulsar-x.y-bin.tar.gz --> Java binaries (No C++ and Python client > > libraries binaries) > > > > In addition, the JAR were being pushed to Sonatype and synced with Maven > > Central. > > > > > > The src and bin packages differs in what it is included : > > * SRC --> Pulsar sources, including bundling a few source files with > > compatible licenses > > * BIN --> Compiled Pulsar Jars and scripts, plus all runtime > dependencies > > > > > > For the SRC artifact: > > * LICENSE: include ASF license + license of additional bundled sources > > * NOTICE: Standard ASF notice (no additional notices for the sources we > > are bundling) > > > > For the BIN artifact: > > * LICENSE: > > - Include ASF License > > - Include Licenses for all bundled dependency jars, adding them in > a > > folder like: > > licences/LICENSE-HdrHistogram.txt > > and then mentioning in LICENSE file: > > Eg: "HdrHistogram -- HdrHistogram-*.jar -- BSD 2-Clause License" > > - Include licenses > > > > * NOTICE: > > - Include Pulsar ASF copyright > > - Include copyright lines for all the bundled dependencies > > - Include additional content from NOTICE files from the bundled > > dependencies > > > > In both artifacts, include a DISCLAIMER file with the ASF incubator > > disclaimer text. > > > > > > Is that a fair understanding or am I missing something? > > > > Matteo > > > > > > -- > > Matteo Merli > > <[email protected]> > > > > On Mon, Jul 10, 2017 at 3:00 PM, Matteo Merli <[email protected]> wrote: > > > > > Ok, Thanks for the clarification. > > > > > > I still need to read thoroughly the release process documentation. Then > > > I'll try to give it a shot at fixing the LICENSE and NOTICE files. > > > > > > -- > > > Matteo Merli > > > <[email protected]> > > > > > > On Mon, Jul 10, 2017 at 2:28 PM, Dave Fisher <[email protected]> > > > wrote: > > > > > >> Hi Matteo, > > >> > > >> The ZLIB license needs to go into the LICENSE file. Only put something > > >> into NOTICE for required copyright and/or other attribution. > > >> > > >> Thanks, > > >> Dave > > >> > > >> Sent from my iPhone > > >> > > >> > On Jul 10, 2017, at 2:19 PM, Matteo Merli <[email protected]> > > >> wrote: > > >> > > > >> > I was about to ask on the Legal-discuss forum, but then I have > looked > > a > > >> bit > > >> > more and verified that the license for the CRC32-C code is the ZLib > > >> > license, which according to https://www.apache.org/legal/ > > resolved.html > > >> > belongs to the Category-A and can be included in the source > > >> distribution. > > >> > > > >> > I think we should just need to list it in the NOTICE file and that > > >> should > > >> > be all. > > >> > > > >> > -- > > >> > Matteo Merli > > >> > <[email protected]> > > >> > > > >> > On Mon, Jun 26, 2017 at 12:14 PM, Matteo Merli < > > [email protected]> > > >> > wrote: > > >> > > > >> >> On Mon, Jun 26, 2017 at 11:49 AM, Dave Fisher < > [email protected] > > > > > >> >> wrote: > > >> >> > > >> >>> You should open up a LEGAL lira to discuss on the legal-discuss > > email > > >> >>> list. > > >> >>> > > >> >>> I think that we will need to put some information in the NOTICE, > but > > >> some > > >> >>> will consider the source note as required to be enough. > > >> >>> > > >> >>> Another question is if the special license must be in the LICENSE > > >> file. > > >> >>> > > >> >> > > >> >> > > >> >> Thanks, I'll follow up on this. > > >> >> > > >> >> > > >> >> -- > > >> >> Matteo Merli > > >> >> <[email protected]> > > >> >> > > >> > > >> > > > > > >
