All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 7/8] oprofile: add license information
Date: Tue, 04 Dec 2012 22:55:05 +0100	[thread overview]
Message-ID: <50BE7139.4000405@mind.be> (raw)
In-Reply-To: <1354270483-32356-8-git-send-email-spdawson@gmail.com>

On 30/11/12 11:14, spdawson at gmail.com wrote:
> From: Simon Dawson<simond@trainfx.com>
>
> Signed-off-by: Simon Dawson<simond@trainfx.com>
> ---
>   package/oprofile/oprofile.mk |    2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/package/oprofile/oprofile.mk b/package/oprofile/oprofile.mk
> index 54c46dd..17d225a 100644
> --- a/package/oprofile/oprofile.mk
> +++ b/package/oprofile/oprofile.mk
> @@ -6,6 +6,8 @@
>
>   OPROFILE_VERSION = 0.9.7
>   OPROFILE_SITE = http://downloads.sourceforge.net/project/oprofile/oprofile/oprofile-$(OPROFILE_VERSION)
> +OPROFILE_LICENSE = GPLv2

  Only a few files specify the license, but the ones that do specify
"or later" - including the man page. So it should be GPLv2+.

  (libjvmti, libjvmpi and libopagent libraries are LGPLv2.1+, for which no
license file is included. However, since we don't install to staging, this
is probably not relevant.)


  Regards,
  Arnout

> +OPROFILE_LICENSE_FILES = COPYING
>   OPROFILE_CONF_OPT = --localstatedir=/var --with-kernel-support
>   OPROFILE_BINARIES = utils/ophelp pp/opannotate pp/oparchive pp/opgprof
>   OPROFILE_BINARIES += pp/opreport opjitconv/opjitconv daemon/oprofiled

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-12-04 21:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30 10:14 [Buildroot] [PATCH 0/8] various packages: add license information spdawson at gmail.com
2012-11-30 10:14 ` [Buildroot] [PATCH 1/8] acpid: " spdawson at gmail.com
2012-11-30 20:33   ` Peter Korsgaard
2012-12-01  7:05     ` Simon Dawson
2012-11-30 10:14 ` [Buildroot] [PATCH 2/8] argus: " spdawson at gmail.com
2012-12-04 21:30   ` Arnout Vandecappelle
2012-12-04 21:56     ` Peter Korsgaard
2012-11-30 10:14 ` [Buildroot] [PATCH 3/8] beecrypt: " spdawson at gmail.com
2012-12-04 21:31   ` Arnout Vandecappelle
2012-12-04 21:56     ` Peter Korsgaard
2012-11-30 10:14 ` [Buildroot] [PATCH 4/8] gmp: " spdawson at gmail.com
2012-12-04 21:37   ` Arnout Vandecappelle
2012-12-04 21:55     ` Peter Korsgaard
2012-11-30 10:14 ` [Buildroot] [PATCH 5/8] midori: " spdawson at gmail.com
2012-12-04 21:38   ` Arnout Vandecappelle
2012-12-04 21:56     ` Peter Korsgaard
2012-11-30 10:14 ` [Buildroot] [PATCH 6/8] mpfr: " spdawson at gmail.com
2012-12-04 21:40   ` Arnout Vandecappelle
2012-12-04 21:56     ` Peter Korsgaard
2012-11-30 10:14 ` [Buildroot] [PATCH 7/8] oprofile: " spdawson at gmail.com
2012-12-04 21:55   ` Arnout Vandecappelle [this message]
2012-12-04 22:44     ` Peter Korsgaard
2012-11-30 10:14 ` [Buildroot] [PATCH 8/8] screen: " spdawson at gmail.com
2012-12-04 21:59   ` Arnout Vandecappelle
2012-12-04 22:50     ` Peter Korsgaard

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=50BE7139.4000405@mind.be \
    --to=arnout@mind.be \
    --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.