All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: Armin Kuster <akuster808@gmail.com>
Cc: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] meta-networking: fping license
Date: Sat, 18 Sep 2021 12:50:17 -0700	[thread overview]
Message-ID: <CAMKF1soS4f_4KqwBVZOPu5ks8VJsAtwzMDVM6Xk15RGW9Va==w@mail.gmail.com> (raw)
In-Reply-To: <01841159-90c6-ba5f-62e6-b4e5859a770e@gmail.com>

it seems like stanford version of BSD-3 see debian's license file
https://tracker.debian.org/media/packages/f/fping/copyright-4.2-1

On Sat, Sep 18, 2021 at 12:10 PM Armin Kuster <akuster808@gmail.com> wrote:
>
> Hello,
>
> The LICENSE listed in this recipe is "BSD" and it clearly is not that
> nor could I find the below wording matching any of the BSD variants (
> Not a Lawyer). Now that SPDX data can be generated easier from core,
> this may barf with the invalid "License".  This is the last outstanding
> invalid BSD license in meta-oe and if anyone uses this package, maybe
> you can dig into finding out what the proper license should be.
>
> - Armin
>
>
> Constance of 'COPYING':
>
> * Original author:  Roland Schemers  <schemers@stanford.edu>
>  * IPv6 Support:     Jeroen Massar    <jeroen@unfix.org / jeroen@ipng.nl>
>  * Improved main loop: David Schweikert <david@schweikert.ch>
>  * Debian Merge, TOS settings: Tobi Oetiker <tobi@oetiker.ch>
>  * Bugfixes, byte order & senseful seq.-numbers: Stephan Fuhrmann
> (stephan.fuhrmann AT 1und1.de)
>  *
>  * Redistribution and use in source and binary forms are permitted
>  * provided that the above copyright notice and this paragraph are
>  * duplicated in all such forms and that any documentation,
>  * advertising materials, and other materials related to such
>  * distribution and use acknowledge that the software was developed
>  * by Stanford University.  The name of the University may not be used
>  * to endorse or promote products derived from this software without
>  * specific prior written permission.
>  * THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
>  * IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
>  * WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
>
>
> 
>

      reply	other threads:[~2021-09-18 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 19:10 meta-networking: fping license Armin Kuster
2021-09-18 19:50 ` Khem Raj [this message]

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='CAMKF1soS4f_4KqwBVZOPu5ks8VJsAtwzMDVM6Xk15RGW9Va==w@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=akuster808@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.