From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fbv: add license info
Date: Sun, 09 Dec 2012 16:05:49 +0100 [thread overview]
Message-ID: <50C4A8CD.2090407@mind.be> (raw)
In-Reply-To: <1354875156-28654-1-git-send-email-sho@relinux.de>
On 07/12/12 11:12, Stephan Hoffmann wrote:
> Signed-off-by: Stephan Hoffmann<sho@relinux.de>
> ---
> package/fbv/fbv.mk | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/package/fbv/fbv.mk b/package/fbv/fbv.mk
> index 7949e99..f697fe8 100644
> --- a/package/fbv/fbv.mk
> +++ b/package/fbv/fbv.mk
> @@ -7,6 +7,9 @@ FBV_VERSION:=1.0b
> FBV_SOURCE:=fbv-$(FBV_VERSION).tar.gz
> FBV_SITE:=http://s-tech.elsat.net.pl/fbv
>
> +FBV_LICENSE = GPLv2
Although the README and COPYING files claim it's version 2, all source files
say version 2 or later.
I'm not sure what to do here. The safe option is:
FBV_LICENSE = GPLv2 (or later?)
> +FBV_LICENSE_FILES = COPYING
That file is just referring to the GNU website, so it doesn't help much
to use that as the license file. Still, it's better than nothing I guess.
Regards,
Arnout
> +
> ### image format dependencies and configure options
> FBV_DEPENDENCIES = # empty
> FBV_CONFIGURE_OPTS = # empty
--
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
next prev parent reply other threads:[~2012-12-09 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 10:12 [Buildroot] [PATCH] fbv: add license info Stephan Hoffmann
2012-12-09 15:05 ` Arnout Vandecappelle [this message]
2012-12-09 20:44 ` Peter Korsgaard
2012-12-16 10:33 ` 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=50C4A8CD.2090407@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox