From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] sam-ba: add license information
Date: Wed, 17 Apr 2013 07:46:01 +0200 [thread overview]
Message-ID: <516E3719.3000502@mind.be> (raw)
In-Reply-To: <CAHt8ZCM50Px59NfArH=xeOeGH1mvnmtN7tS8m01Euv5rQo87oQ@mail.gmail.com>
On 15/04/13 10:40, Simon Dawson wrote:
> Hi Thomas, thanks for looking at this.
>
> On 15 April 2013 09:32, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> >Simon,
>> >
>> >On Mon, 15 Apr 2013 08:19:00 +0100,spdawson at gmail.com wrote:
>> >
>>> >>+SAM_BA_LICENSE = BSD-like
>>> >>+SAM_BA_LICENSE_FILES = doc/readme.txt
>> >
>> >Hum, is this really the case? I thought the source code for it was not
>> >available? Well, it's true that a binary-only program can carry a BSD
>> >license... but to me, having 'BSD-like' license on a binary-only
>> >program sounds a bit odd.
> Yes, agreed. I'm not sure what the right approach is, given that
> sam-ba as distributed is a mixture of pre-built binaries, and (C and
> Tcl) source code. Perhaps we just say "sam-ba license", which may be
> less contentious...?
I do like the "BSD-like" qualifier, though, because it tells you a lot
more. How about "BSD-like (partly binary-only)"?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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:[~2013-04-17 5:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 7:19 [Buildroot] [PATCH] sam-ba: add license information spdawson at gmail.com
2013-04-15 8:32 ` Thomas Petazzoni
2013-04-15 8:40 ` Simon Dawson
2013-04-17 5:46 ` Arnout Vandecappelle [this message]
2013-04-17 7:52 ` Thomas Petazzoni
2013-04-17 8:00 ` Simon Dawson
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=516E3719.3000502@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