From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/6] sg3_utils: new package
Date: Tue, 08 Jan 2013 09:05:16 +0100 [thread overview]
Message-ID: <50EBD33C.1090603@mind.be> (raw)
In-Reply-To: <201301072256.26160.yann.morin.1998@free.fr>
On 07/01/13 22:56, Yann E. MORIN wrote:
> Thomas, Belisko, All,
>
> On Monday 07 January 2013 Thomas Petazzoni wrote:
>> On Mon, 7 Jan 2013 22:45:50 +0100, Belisko Marek wrote:
>>>> You should be work specific than just BSD and GPL. Like BSD-3c or
>>>> BSD-4c, GPLv2, GPLv2+, GPLv3, GPLv3+, etc.
>>> After proper reading of COPYING file it seems it GPLv2+
>>> "Some of the older utilities are covered by the GPL. More precisely:
>>> You are free to distribute this software under the terms of the
>>> GNU General Public License either version 2, or (at your option)
>>> any later version." but in same file there is no mention about BSD
>>> license version.
>>
>> There is a BSD_LICENSE file that contains a BSD three clause license,
>
> Actually, what matters in the content of the source files. Do some of
> them refer to either license?
> - if the files only refer to GPLv2+, then the BSD-3c does not apply,
> - if the files only refer to BSD-3c, then the GPLv2+ does not apply,
> - if some file refer to one or two of the licenses, then both apply.
- if all files refer to GPLv2+ and BSD-3c, then either applies.
Putting GPLv2+ BSD-3c implies that parts are GPLv2+, other parts and
BSD-3c. But it's also possible (and likely) that either applies. BTW,
it's not possible that both apply because they have conflicting terms.
Regards,
Arnout
>
> (/me likes how he managed to line up the above! ;-) )
>
> Regards,
> Yann E. MORIN.
>
--
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-01-08 8:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 20:43 [Buildroot] [PATCH v2 0/6] Add support for udisks package Marek Belisko
2013-01-07 20:43 ` [Buildroot] [PATCH v2 1/6] sg3_utils: new package Marek Belisko
2013-01-07 21:26 ` Thomas Petazzoni
2013-01-07 21:45 ` Belisko Marek
2013-01-07 21:52 ` Thomas Petazzoni
2013-01-07 21:56 ` Yann E. MORIN
2013-01-08 8:05 ` Arnout Vandecappelle [this message]
2013-01-15 20:48 ` Belisko Marek
2013-01-15 20:59 ` Yann E. MORIN
2013-01-15 21:04 ` Belisko Marek
2013-01-15 21:29 ` Yann E. MORIN
2013-01-16 8:17 ` Arnout Vandecappelle
2013-01-07 20:43 ` [Buildroot] [PATCH v2 2/6] polkit: " Marek Belisko
2013-01-07 21:26 ` Thomas Petazzoni
2013-01-07 21:31 ` Thomas Petazzoni
2013-01-07 20:43 ` [Buildroot] [PATCH v2 3/6] libatasmart: " Marek Belisko
2013-01-07 21:30 ` Thomas Petazzoni
2013-01-07 21:52 ` Belisko Marek
2013-01-07 21:53 ` Thomas Petazzoni
2013-01-07 20:43 ` [Buildroot] [PATCH v2 4/6] lvm2: Install devmapper.pc to staging/target pkgconfig directory Marek Belisko
2013-01-07 20:43 ` [Buildroot] [PATCH v2 5/6] lvm2: Compile and install application library Marek Belisko
2013-01-07 21:38 ` Thomas Petazzoni
2013-01-07 21:58 ` Belisko Marek
2013-01-15 20:53 ` Belisko Marek
2013-01-16 8:06 ` Thomas Petazzoni
2013-01-16 8:49 ` Belisko Marek
2013-02-03 14:20 ` Peter Korsgaard
2013-02-03 20:44 ` Belisko Marek
2013-02-03 21:47 ` Peter Korsgaard
2013-01-07 20:43 ` [Buildroot] [PATCH v2 6/6] udisks: new package Marek Belisko
2013-01-07 21:47 ` Thomas Petazzoni
2013-01-07 22:03 ` Belisko Marek
2013-01-07 22:18 ` Thomas Petazzoni
2013-01-07 22:25 ` Belisko Marek
2013-01-07 22:49 ` Thomas Petazzoni
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=50EBD33C.1090603@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.