aboutsummaryrefslogtreecommitdiffstats
path: root/meta-oe/licenses
diff options
context:
space:
mode:
authorOtavio Salvador <otavio@ossystems.com.br>2014-12-26 15:13:17 -0200
committerMartin Jansa <Martin.Jansa@gmail.com>2014-12-31 16:32:30 +0100
commita5a9697cf6b24ccfb588759798a08f36d1e67fc5 (patch)
tree5811a2841508e8d1a456a80379a6752a754c5728 /meta-oe/licenses
parentf2833950bede6982a3cd761b92083d7be9ab33bf (diff)
downloadmeta-openembedded-contrib-a5a9697cf6b24ccfb588759798a08f36d1e67fc5.tar.gz
meta-openembedded-contrib-a5a9697cf6b24ccfb588759798a08f36d1e67fc5.tar.bz2
meta-openembedded-contrib-a5a9697cf6b24ccfb588759798a08f36d1e67fc5.zip
nbench-byte: Fix license QA error
The license is not a common only and seems to be a 'free distribution' license but without explicit rules about modification or similar. Due that, we copied the license text from the README file and added it onto nbench-byte license file. This fixes following QA error: ,---- | WARNING: Recipe nbench-byte, LICENSE (freely distributable) has | invalid format, LICENSES must have operator "([&|() ])" between | them. `---- Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Diffstat (limited to 'meta-oe/licenses')
-rw-r--r--meta-oe/licenses/nbench-byte10
1 files changed, 10 insertions, 0 deletions
diff --git a/meta-oe/licenses/nbench-byte b/meta-oe/licenses/nbench-byte
new file mode 100644
index 0000000000..7e47ba62b4
--- /dev/null
+++ b/meta-oe/licenses/nbench-byte
@@ -0,0 +1,10 @@
+THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.