From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH for-next 3/3] package/ogre: new package
Date: Sat, 1 Jun 2019 11:24:56 +0200 [thread overview]
Message-ID: <20190601112456.50402535@windsurf> (raw)
In-Reply-To: <20190529151655.7098-3-romain.naour@gmail.com>
Hello Romain,
On Wed, 29 May 2019 17:16:55 +0200
Romain Naour <romain.naour@gmail.com> wrote:
> +OGRE_VERSION = 1.12.0
> +OGRE_SITE = $(call github,OGRECave,ogre,v$(OGRE_VERSION))
> +OGRE_LICENSE = MIT with exceptions (main library), MIT (DeferredShadingMedia samples), Public Domain (samples and plugins), Zlib (tinyxml)
Could you comment a bit on where you found those license terms ? The
LICENSE file only contains the normal MIT license text. Just picking a
random file (OgreFileSystem.cpp) from the main library shows just the
regular MIT license (I don't see any exception).
PlugIns/CgProgramManager/src/OgreCgPlugin.cpp which is a plugin, shows
a MIT license.
Could you perhaps add a comment above this line that justifies this
licensing description ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-06-01 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 15:16 [Buildroot] [PATCH for-next 1/3] package/zziplib: new package Romain Naour
2019-05-29 15:16 ` [Buildroot] [PATCH for-next 2/3] package/swig: enable PCRE regex matching in host-swig Romain Naour
2019-06-01 7:28 ` Thomas Petazzoni
2019-06-01 8:44 ` Peter Korsgaard
2019-06-01 11:09 ` Yann E. MORIN
2019-06-04 20:21 ` Arnout Vandecappelle
2019-05-29 15:16 ` [Buildroot] [PATCH for-next 3/3] package/ogre: new package Romain Naour
2019-06-01 9:24 ` Thomas Petazzoni [this message]
2019-06-01 22:00 ` Romain Naour
2019-10-27 15:44 ` Thomas Petazzoni
2019-06-01 7:22 ` [Buildroot] [PATCH for-next 1/3] package/zziplib: " 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=20190601112456.50402535@windsurf \
--to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox