All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libunwind:  new package
Date: Mon, 24 Jun 2013 16:29:37 +0200	[thread overview]
Message-ID: <20130624162937.75f6c3fd@skate> (raw)
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C639A6B89D@ex-mb1.corp.adtran.com>

Hello,

On Mon, 24 Jun 2013 14:24:55 +0000, ANDY KENNEDY wrote:

> Thomas:  To what shall I set the License variable?
> 
> I have NO IDEA what it should be.  This isn't GPL code, not
> MIT, not BSD, nothing I've seen before.  All I know is that it
> is free of any restrictions, though copyrighted by HP.
> 
> Andy
> 
> License text:
> 
> Copyright (c) 2002 Hewlett-Packard Co.
> 
> 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.

Seeing this, I would probably do something like:

LIBUNWIND_LICENSE = libunwind license (BSD-like)

or something like that.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-06-24 14:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21 23:03 [Buildroot] [PATCH] libunwind: new package ANDY KENNEDY
2013-06-22  9:15 ` Thomas Petazzoni
2013-06-24 14:24   ` ANDY KENNEDY
2013-06-24 14:29     ` Thomas Petazzoni [this message]
2013-06-24 16:56     ` Arnout Vandecappelle
2013-06-25 17:53       ` ANDY KENNEDY
2013-06-25 21:08         ` Arnout Vandecappelle
2013-06-25 21:38           ` ANDY KENNEDY
  -- strict thread matches above, loose matches on Subject: below --
2013-06-24 14:39 ANDY KENNEDY

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=20130624162937.75f6c3fd@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.