mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: Roland Hieber <rhi@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v3] python3-numpy: New package
Date: Thu, 14 Nov 2019 19:50:15 +0100	[thread overview]
Message-ID: <CABDcavbvrvJb-ufhBhUw66i5CObEWdrNVZeu55nZ_3Zn+0Kq_g@mail.gmail.com> (raw)
In-Reply-To: <20191114133129.purhfumplzkmpgwd@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 4466 bytes --]

El jue., 14 nov. 2019 a las 14:31, Roland Hieber (<rhi@pengutronix.de>)
escribió:

> On Thu, Nov 14, 2019 at 12:40:43PM +0100, Guillermo Rodriguez Garcia wrote:
> > El jue., 14 nov. 2019 a las 12:18, Roland Hieber (<rhi@pengutronix.de>)
> > escribió:
> >
> > > On Thu, Nov 14, 2019 at 11:07:16AM +0100, Guillermo Rodriguez Garcia
> wrote:
> > > > El jue., 14 nov. 2019 a las 10:56, Roland Hieber (<
> rhi@pengutronix.de>)
> > > > escribió:
> > > >
> > > > > > > numpy/core/src/multiarray/dragon4.c seems to be a license found
> > > nowhere
> > > > > > > else, so I would also add "AND UNKNOWN" to
> PYTHON3_NUMPY_LICENSE
> > > and
> > > > > add
> > > > > > > its verbatim license text with startline and endline
> parameters in
> > > > > > > PYTHON3_NUMPY_LICENSE_FILES. PTXdist extracts all those license
> > > > > > > texts mentioned in that variable and adds them to the license
> > > report,
> > > > > > > so it doesn't get lost too :)
> > > > >
> > > >
> > > > On re-reading this: The license in dragon4.c is just MIT. So while
> it is
> > > OK
> > > > to add it to LICENSE_FILES I think we should not add the "AND
> unknown"
> > > bit.
> > >
> > > Oh. I just blindly believed LICENSE.txt. But now that you say it, my
> > > license matcher identifies it as "Zlib", not as "MIT".
> > >
> >
> > Uhm, doesn't look like Zlib to me; here's the license text extracted from
> > dragon4.c:
> >
> > /*
> >  * Copyright (c) 2014 Ryan Juckett
> >  *
> >  * Permission is hereby granted, free of charge, to any person obtaining
> a
> > copy
> >  * of this software and associated documentation files (the "Software"),
> to
> >  * deal in the Software without restriction, including without limitation
> > the
> >  * rights to use, copy, modify, merge, publish, distribute, sublicense,
> > and/or
> >  * sell copies of the Software, and to permit persons to whom the
> Software
> > is
> >  * furnished to do so, subject to the following conditions:
> >  *
> >  * The above copyright notice and this permission notice shall be
> included
> > in
> >  * all copies or substantial portions of the Software.
> >  *
> >  * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
> EXPRESS
> > OR
> >  * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
> MERCHANTABILITY,
> >  * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
> SHALL
> > THE
> >  * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
> >  * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
> ARISING
> >  * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
> > DEALINGS
> >  * IN THE SOFTWARE.
> >  */
> >
> > And here are the MIT and Zlib licenses:
> >
> > https://spdx.org/licenses/MIT.html
> > https://spdx.org/licenses/Zlib.html
> >
> > I would say that the license is indeed MIT, which is what LICENSE.txt
> says:
> >
> > Name: dragon4
> > Files: numpy/core/src/multiarray/dragon4.c
> > License: MIT
> >   For license text, see numpy/core/src/multiarray/dragon4.c
>
> We're looking at different versions of the code. Your make file
> specifies 1.16.1, and indeed that license was changed in commit
> 2babaaa12 ("LICENSE: update dragon4 license to MIT.") [1], which landed
> in numpy 1.17.4. The _LICENSE vars should describe the version in the
> make file.
>

Ops. You are right. I didn't realize the license had changed so I mixed
things up.


>
> Do you want to send a version-bump to the new version
> instead? ;-)
>

The reason why I did not do that is that 1.17.x releases break
cross-compilation.
I reported this (https://github.com/numpy/numpy/issues/14861) a few days
ago and it has been fixed since then.

So I guess yes, the best is to upgrade to 1.17.4 (will need to include a
patch for the issue linked above, since the fix has not made it to any
public release yet)

Thank you,

Guillermo


>
> [1]:
> https://github.com/numpy/numpy/commit/2babaaa123c64c9f8d47d5b8b05942ab2c79a4e3
>
>   - Roland
>
>
> --
> Roland Hieber, Pengutronix e.K.          | r.hieber@pengutronix.de     |
> Steuerwalder Str. 21                     | https://www.pengutronix.de/ |
> 31137 Hildesheim, Germany                | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686         | Fax:   +49-5121-206917-5555 |
>


-- 
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

[-- Attachment #1.2: Type: text/html, Size: 6563 bytes --]

[-- Attachment #2: Type: text/plain, Size: 92 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2019-11-14 18:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11 15:13 [ptxdist] [PATCH] " Guillermo Rodríguez
2019-11-12  9:32 ` [ptxdist] [PATCH v2] " Guillermo Rodríguez
2019-11-12  9:51 ` [ptxdist] [PATCH] " Roland Hieber
2019-11-12 11:48   ` Guillermo Rodriguez Garcia
2019-11-12 11:51   ` [ptxdist] [PATCH v3] " Guillermo Rodríguez
2019-11-13  9:36     ` Roland Hieber
2019-11-14  9:36       ` Guillermo Rodriguez Garcia
2019-11-14  9:56         ` Roland Hieber
2019-11-14 10:01           ` Guillermo Rodriguez Garcia
2019-11-14 10:03             ` [ptxdist] [PATCH v4] " Guillermo Rodríguez
2019-11-14 10:07           ` [ptxdist] [PATCH v3] " Guillermo Rodriguez Garcia
2019-11-14 10:09             ` [ptxdist] [PATCH v5] " Guillermo Rodríguez
2019-11-14 20:24               ` Ladislav Michl
2019-11-14 11:18             ` [ptxdist] [PATCH v3] " Roland Hieber
2019-11-14 11:40               ` Guillermo Rodriguez Garcia
2019-11-14 13:31                 ` Roland Hieber
2019-11-14 18:50                   ` Guillermo Rodriguez Garcia [this message]
2019-11-15  8:51                     ` [ptxdist] [PATCH v6] " Guillermo Rodríguez
2019-11-15 14:19                       ` Michael Olbrich
2019-11-15 20:11                         ` [ptxdist] [PATCH] " Guillermo Rodriguez Garcia
2019-11-19  9:10                           ` Guillermo Rodriguez Garcia
2019-11-19  9:23                             ` Michael Olbrich
2019-11-19 10:15                               ` Guillermo Rodriguez Garcia
2019-11-19 12:39                                 ` [ptxdist] [PATCH v7] " Guillermo Rodríguez
2019-11-25  6:32                                   ` Michael Olbrich
2019-11-25  9:35                                     ` Guillermo Rodriguez Garcia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABDcavbvrvJb-ufhBhUw66i5CObEWdrNVZeu55nZ_3Zn+0Kq_g@mail.gmail.com \
    --to=guille.rodriguez@gmail.com \
    --cc=ptxdist@pengutronix.de \
    --cc=rhi@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox