Yes, I agree. My mind must have wondered a bit after doing cut and paste all day long. I will change those headers if the RC is rejected.
jerry On Thu, Jul 21, 2016 at 11:06 AM, Marshall Schor <[email protected]> wrote: > ok, thanks. > > This licensing work is **impressive** and gets better each time :-) > > I was confused by the format a bit. The part earlier in the file appeared > to be > a list of lists: > > outer list: the license > > inner list: the components licensed using the out list license. > > So when I see just the component, I didn't interpret that correctly. > > -------- > > Later in the file, where there's the name of a license, followed by the > license > text, that is introduced by boiler plate: > > ========================================================================== > == The following products are licensed: <<< name of license >>> > ========================================================================== > > Of course, that's the wrong comment. because following this is the > license, not > the list of things licensed under that license. It would seem that comment > block would be appropriate for the first part of the license file, which > does > list the components licensed under some license-name. > > -Marshall > > On 7/21/2016 10:50 AM, Jaroslaw Cwiklik wrote: > > Search the LICENSE for futures, st4, six-1, and jLine. All licenses > (text) > > are included for these in the LICENSE file. > > > > There are lots of dependencies in DUCC so I will consider a different > > approach for the next release. > > Jerry > > > > > > > > On Thu, Jul 21, 2016 at 10:07 AM, Marshall Schor <[email protected]> wrote: > > > >> In the bin / tar LICENSE there are lines like: > >> > >> === six-1.7.3-py2.py3-none-any.zip === > >> > >> === ST4-4.0.8.jar ==================== > >> > >> what do these mean? > >> > >> > ----------------------------------------------------------------------------------------------------------- > >> There are also references to licenses by name: > >> === jLine License ================== > >> (cassandra) jline-1.0.jar > >> > >> === Futures License ========== > >> (cassandra) futures-2.1.6-py2.py3-none-any.zip > >> > >> but it's not obvious from this where to find the actual license in the > >> distribution. > >> > >> > ---------------------------------------------------------------------------------------------------------- > >> Cassandra has a particular approach to license management which > >> a) manages a huge number of licenses > >> b) includes all of them in an organized way in their binary distribution > >> > >> Perhaps we could do something similar? > >> > >> -Marshall > >> > >
