summaryrefslogtreecommitdiffstats
path: root/meta/files/common-licenses/IEC-Code-Components-EULA
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2025-11-07 13:31:53 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2025-11-07 13:31:53 +0000
commit8c22ff0d8b70d9b12f0487ef696a7e915b9e3173 (patch)
treeefdc32587159d0050a69009bdf2330a531727d95 /meta/files/common-licenses/IEC-Code-Components-EULA
parentd412d2747595c1cc4a5e3ca975e3adc31b2f7891 (diff)
downloadpoky-8c22ff0d8b70d9b12f0487ef696a7e915b9e3173.tar.gz
The poky repository master branch is no longer being updated.
You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/files/common-licenses/IEC-Code-Components-EULA')
-rw-r--r--meta/files/common-licenses/IEC-Code-Components-EULA37
1 files changed, 0 insertions, 37 deletions
diff --git a/meta/files/common-licenses/IEC-Code-Components-EULA b/meta/files/common-licenses/IEC-Code-Components-EULA
deleted file mode 100644
index b74269afd9..0000000000
--- a/meta/files/common-licenses/IEC-Code-Components-EULA
+++ /dev/null
@@ -1,37 +0,0 @@
1IEC Code Components End-user licence agreement
2
3Code Components in IEC standards (International Standards, Technical Specifications or
4Technical Reports) which have been identified and approved for licensing, are licensed subject to
5the following conditions:
6
7- Redistributions of software must retain the Copyright Notice, this list of conditions and the
8disclaimer below (“Disclaimer”).
9- The software license extends to modifications permitted under the relevant IEC standard.
10- The software license extends to clarifications and corrections approved by IEC.
11- Neither the name of IEC, nor the names of specific contributors, may be used to endorse or
12promote products derived from this software without specific prior written permission. The
13relevant IEC standard may be referenced when claiming compliance with the relevant IEC
14standard.
15- The user of Code Components shall attribute each such Code Component to IEC and identify
16the IEC standard from which it is taken. Such attribution (e.g., “This code was derived from IEC
17[insert standard reference number:publication year] within modifications permitted in the
18relevant IEC standard. Please reproduce this note if possible.”), may be placed in the code itself
19or any other reasonable location.
20
21Code Components means components included in IEC standards that are intended to be directly
22processed by a computer and also includes any text found between the markers <CODE
23BEGINS> and <CODE ENDS>, or otherwise clearly labeled in this standard as a Code
24Component.
25
26The Disclaimer is:
27EACH OF THE CODE COMPONENTS IS PROVIDED BY THE COPYRIGHT HOLDERS AND
28CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
29NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
30PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
31OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
32EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
33PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
34PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
35LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
36NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THE CODE
37COMPONENTS, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.