reuse: Fix reuse compliance issues
Only those licenses that are explicitly mention in the SPDX headers in the
repository are allowed to have license text files present. That means, that in
the LICENSE directory we can only have licenses for meta-data files and not
licenses for packages that this meta-data is used to build.
Signed-off-by:
Robert Drab <robert.drab@huawei.com>
parent
b76ccdda
No related branches found
No related tags found
Showing
- LICENSES/Apache-2.0.txt 0 additions, 0 deletionsLICENSES/Apache-2.0.txt
- LICENSES/BSD-3-Clause 0 additions, 11 deletionsLICENSES/BSD-3-Clause
- LICENSES/GPL-2.0-or-later 0 additions, 319 deletionsLICENSES/GPL-2.0-or-later
- LICENSES/MulanPSL-2.0 0 additions, 131 deletionsLICENSES/MulanPSL-2.0
- recipes-core/busybox/busybox/openharmony.cfg.license 3 additions, 0 deletionsrecipes-core/busybox/busybox/openharmony.cfg.license
- recipes-openharmony/openharmony/files/accesstoken.service.license 3 additions, 0 deletions...openharmony/openharmony/files/accesstoken.service.license
- recipes-openharmony/openharmony/files/appspawn.service.license 3 additions, 0 deletions...es-openharmony/openharmony/files/appspawn.service.license
- recipes-openharmony/openharmony/files/dsoftbus.service.license 3 additions, 0 deletions...es-openharmony/openharmony/files/dsoftbus.service.license
- recipes-openharmony/openharmony/files/hilogd.service.license 3 additions, 0 deletionsrecipes-openharmony/openharmony/files/hilogd.service.license
- recipes-openharmony/openharmony/files/samgr.service.license 3 additions, 0 deletionsrecipes-openharmony/openharmony/files/samgr.service.license
- recipes-openharmony/openharmony/files/tokensync.service.license 3 additions, 0 deletions...s-openharmony/openharmony/files/tokensync.service.license
File moved
LICENSES/BSD-3-Clause
deleted
100644 → 0
LICENSES/GPL-2.0-or-later
deleted
100644 → 0
LICENSES/MulanPSL-2.0
deleted
100644 → 0
Please register or sign in to comment