yuzu-emu
/
yuzu
Archived
1
0
Fork 0
Code
This repository has been archived on 2024-03-23. You can view files and clone it, but cannot push or open issues or pull requests.
yuzu/.ci/scripts/common/post-upload.sh

21 lines
641 B
Bash
Raw Normal View History

Finalize Azure Pipelines Definitions d
2019-07-14 01:34:40 +00:00
#!/bin/bash -ex
chore: make yuzu REUSE compliant [REUSE] is a specification that aims at making file copyright information consistent, so that it can be both human and machine readable. It basically requires that all files have a header containing copyright and licensing information. When this isn't possible, like when dealing with binary assets, generated files or embedded third-party dependencies, it is permitted to insert copyright information in the `.reuse/dep5` file. Oh, and it also requires that all the licenses used in the project are present in the `LICENSES` folder, that's why the diff is so huge. This can be done automatically with `reuse download --all`. The `reuse` tool also contains a handy subcommand that analyzes the project and tells whether or not the project is (still) compliant, `reuse lint`. Following REUSE has a few advantages over the current approach: - Copyright information is easy to access for users / downstream - Files like `dist/license.md` do not need to exist anymore, as `.reuse/dep5` is used instead - `reuse lint` makes it easy to ensure that copyright information of files like binary assets / images is always accurate and up to date To add copyright information of files that didn't have it I looked up who committed what and when, for each file. As yuzu contributors do not have to sign a CLA or similar I couldn't assume that copyright ownership was of the "yuzu Emulator Project", so I used the name and/or email of the commit author instead. [REUSE]: https://reuse.software Follow-up to 01cf05bc75b1e47beb08937439f3ed9339e7b254
2022-05-15 00:06:02 +00:00
# SPDX-FileCopyrightText: 2019 yuzu Emulator Project
# SPDX-License-Identifier: GPL-2.0-or-later
Finalize Azure Pipelines Definitions d
2019-07-14 01:34:40 +00:00
# Copy documentation
chore: make yuzu REUSE compliant [REUSE] is a specification that aims at making file copyright information consistent, so that it can be both human and machine readable. It basically requires that all files have a header containing copyright and licensing information. When this isn't possible, like when dealing with binary assets, generated files or embedded third-party dependencies, it is permitted to insert copyright information in the `.reuse/dep5` file. Oh, and it also requires that all the licenses used in the project are present in the `LICENSES` folder, that's why the diff is so huge. This can be done automatically with `reuse download --all`. The `reuse` tool also contains a handy subcommand that analyzes the project and tells whether or not the project is (still) compliant, `reuse lint`. Following REUSE has a few advantages over the current approach: - Copyright information is easy to access for users / downstream - Files like `dist/license.md` do not need to exist anymore, as `.reuse/dep5` is used instead - `reuse lint` makes it easy to ensure that copyright information of files like binary assets / images is always accurate and up to date To add copyright information of files that didn't have it I looked up who committed what and when, for each file. As yuzu contributors do not have to sign a CLA or similar I couldn't assume that copyright ownership was of the "yuzu Emulator Project", so I used the name and/or email of the commit author instead. [REUSE]: https://reuse.software Follow-up to 01cf05bc75b1e47beb08937439f3ed9339e7b254
2022-05-15 00:06:02 +00:00
cp LICENSE.txt "$DIR_NAME"
ci: Rename build folder only on non-mainline builds
2019-11-07 04:26:29 +00:00
cp README.md "$DIR_NAME"
Finalize Azure Pipelines Definitions d
2019-07-14 01:34:40 +00:00
CI: lint scripts
2022-07-05 03:18:17 +00:00
if [[ -z "${NO_SOURCE_PACK}" ]]; then
ci: Graft source when archiving Instead of including yuzu and all the sources it uses directly, include only what specifically belongs to yuzu. Submodules can be downloaded separately later using git since a shallow clone includes minimally all the repository information needed for it.
2022-07-31 05:25:40 +00:00
git clone --depth 1 file://$(readlink -e .) ${REV_NAME}-source
tar -cJvf "${REV_NAME}-source.tar.xz" ${REV_NAME}-source
CI: upload artifacts for pull request verification
2022-06-19 05:15:30 +00:00
cp -v "${REV_NAME}-source.tar.xz" "$DIR_NAME"
post-upload: Upload Linux source to artifacts dir The source from the Linux build is desireable as it has permissions and line endings set correctly.
2022-08-09 04:18:32 +00:00
cp -v "${REV_NAME}-source.tar.xz" "${ARTIFACTS_DIR}/"
CI: upload artifacts for pull request verification
2022-06-19 05:15:30 +00:00
fi
ci: Package source with builds
2019-11-12 03:32:22 +00:00
ci: Rename build folder only on non-mainline builds
2019-11-07 04:26:29 +00:00
tar $COMPRESSION_FLAGS "$ARCHIVE_NAME" "$DIR_NAME"
Finalize Azure Pipelines Definitions d
2019-07-14 01:34:40 +00:00
# move the compiled archive into the artifacts directory to be uploaded by travis releases
ci: Build an AppImage This builds yuzu in an AppImage alongside the other archives during release. Required to allow distributing yuzu in the future with upgraded dependencies, such as Qt.
2020-12-30 03:09:06 +00:00
mv "$ARCHIVE_NAME" "${ARTIFACTS_DIR}/"