Exclude .git from source RPMs

[stephank]

Description

I had a need to rebuild an old Sunshine for a newer Fedora, and noticed SRPMs are huge (1.3 GB), of which the bulk appears to be .git. A local build without it present seems to work fine, so consider removing it using --exclude-vcs. (Though I don't know how to test your CI.)

Screenshot

Issues Fixed or Closed

Roadmap Issues

Type of Change

• feat: New feature (non-breaking change which adds functionality)
• fix: Bug fix (non-breaking change which fixes an issue)
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
• refactor: Code change that neither fixes a bug nor adds a feature
• perf: Code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit
• BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

• Code follows the style guidelines of this project
• Code has been self-reviewed
• Code has been commented, particularly in hard-to-understand areas
• Code docstring/documentation-blocks for new or existing methods/components have been added or updated
• Unit tests have been added or updated for any new or modified functionality

AI Usage

• None: No AI tools were used in creating this PR
• Light: AI provided minor assistance (formatting, simple suggestions)
• Moderate: AI helped with code generation or debugging specific parts
• Heavy: AI generated most or all of the code changes

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ReenigneArcher]

Thank you for the PR. Could you sign the cla?

[stephank]

Sorry, I prefer not to. But this is so tiny, consider it public domain. Feel free to strip authorship.

[ReenigneArcher]

I think we need the .git directory for the Sunshine build:

• https://github.com/LizardByte/Sunshine/blob/8765bbf050a18dcaf441851e5e52505a6c709c48/packaging/linux/copr/Sunshine.spec#L28
• https://github.com/LizardByte/Sunshine/blob/8765bbf050a18dcaf441851e5e52505a6c709c48/cmake/prep/build_version.cmake#L32

[ReenigneArcher]

The large .git directory in Sunshine is a result of the build-deps submodule.

This has been fixed in the following PRs

• fix!: publish to GitHub releases instead of dist branch build-deps#604
• build(deps): add shallow option to submodules build-deps#611