Commit c6e47644 authored by Peter Senna Tschudin's avatar Peter Senna Tschudin

license-expectations.md: Define artifact and use constraints consistently

This patch adds a description of what an artifact is in regards to
binary packages, and replace a few occurrences of `restrictions` by
`constraints` to address stakeholders feedback from APERTIS-5722.
Signed-off-by: Peter Senna Tschudin's avatarPeter Senna Tschudin <peter.senna@collabora.com>
parent 8502be1c
......@@ -27,7 +27,7 @@ Apertis aims to accomplish the following goals:
distributable, so that downstreams are entitled to
use, modify and redistribute work derived from our deliverables.
- Ensure that Apertis images targeting devices (such as target and minimal),
are not subject to licensing restrictions that may conflict with the regulatory
are not subject to licensing constraints that may conflict with the regulatory
requirements of some intended use cases.
In order to reach these goals, the below assumptions are made:
......@@ -122,11 +122,14 @@ Any package outside these expectations should be documented.
#### target
This component ships source packages producing binary packages used in
images deployable on target devices. Specifically, the binary packages
installed on those images should not be affected by licensing restrictions.
This does not mean that every source or binary package in the component must be
completely unrestricted:
This component ships source packages producing binary packages used in images
deployable on target devices. For a file in a binary package to be considered
an artifact, the file must have been generated/compiled/translated from a
source package. An artifact can be an executable, a library, or any other file
that is subject to a license. Specifically, the binary packages installed on
those images should not be affected by licensing constraints. This does not
mean that every source or binary package in the component must be completely
unrestricted:
* source packages may contain restricted build scripts, provided that the license
does not affect generated artifacts
* source packages may contain restricted tests or utilities, provided that they
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment