ci-package-builder: Hardcode the license blacklist

Rather than relying on variables set up at the subgroup level on GitLab,
hardcode the license blacklist in the definition.

This has two benefits:
* changes to the list of blocked licenses are tracked in git
* licensing checks are still applied on packages in non-standard
  locations such as when forking them
* it gets rid of something that prevents us from moving to a flatter
  hierarchy where all the packages are directly under `pkg/`

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

ci-package-builder.yml

@@ -9,7 +9,7 @@ variables:
   GBP_CONF_FILES: "/dev/null"
   # Disable shallow clone as history is needed for describing tags
   GIT_DEPTH: 0
-  LICENSE_BLACKLIST: ""
+  LICENSE_BLACKLIST_target: "GPL-3 GPL-3+ AGPL-3 AGPL-3+ AGPL-1 AGPL-1+ LGPL-3 LGPL-3+ BSD-4-Clause MPL-1.1"
   OBS_REPOSITORIES: default
   # Set OBS_PREFIX in the project package variables to force uploads to a
   # branch. For instance, by setting it to home:yourusername:branches uploads
@@ -53,6 +53,9 @@ prepare-build-env:
     - test -f debian/apertis/component && COMPONENT=$(cat debian/apertis/component || true)
     - COMPONENT=${COMPONENT:-development} # assume development as fallback
     - echo "COMPONENT=$COMPONENT" | tee -a build.env
+    - LICENSE_BLACKLIST_VAR=LICENSE_BLACKLIST_$COMPONENT # look for variables like "$LICENSE_BLACKLIST_target"
+    - LICENSE_BLACKLIST=${!LICENSE_BLACKLIST_VAR:-}
+    - echo "LICENSE_BLACKLIST='$LICENSE_BLACKLIST'"
   artifacts:
     reports:
       dotenv: build.env