[oe-commits] [meta-openembedded] 01/60: python-numeric: Add LLNL license

[git at git.openembedded.org]

martin_jansa pushed a commit to branch krogoth-next
in repository meta-openembedded.

commit 9f55eeb3b886dca3f9fa918ffd089855eecc6cf5
Author: Armin Kuster <akuster808 at gmail.com>
AuthorDate: Mon May 9 07:42:04 2016 -0700

    python-numeric: Add LLNL license
    
    WARNING: python-numeric-24.2-ml3 do_populate_lic: python-numeric: No generic license file exists for: LLNL in any provider
    
    copied from sources.
    
    Signed-off-by: Armin Kuster <akuster808 at gmail.com>
    Signed-off-by: Martin Jansa <Martin.Jansa at gmail.com>
    (cherry picked from commit 09ccbeb7acc8658abb6a63b75e10a18ddcaffd06)
    Signed-off-by: Armin Kuster <akuster808 at gmail.com>
---
 meta-python/licenses/LLNL | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/meta-python/licenses/LLNL b/meta-python/licenses/LLNL
new file mode 100644
index 0000000..1127d56
--- /dev/null
+++ b/meta-python/licenses/LLNL
@@ -0,0 +1,16 @@
+Legal Notice
+
+*** Legal Notice for all LLNL-contributed files ***
+
+Copyright (c) 1996. The Regents of the University of California. All rights reserved.
+
+Permission to use, copy, modify, and distribute this software for any purpose without
+fee is hereby granted, provided that this entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all copies of the supporting documentation for such software.
+
+This work was produced at the University of California, Lawrence Livermore National
+Laboratory under contract no. W-7405-ENG-48 between the U.S. Department of Energy and The Regents of the University of California for the operation of UC LLNL.
+
+DISCLAIMER
+
+This software was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor the University of California nor any of their employees, makes any warranty, express or implied, or assumes any liability or responsibility for the accuracy, completeness, or usefulness of any
+information, apparatus, product, or process disclosed, or represents that its use would not infringe privately-owned rights. Reference herein to any specific commercial products, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government or the University of California. The views and opinions of authors expressed herein do not necessarily state or reflect t [...]

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.