Skip to content

Remove sparkle-cli (sparkle.app) from binary distribution#2826

Merged
zorgiepoo merged 1 commit into
2.xfrom
push-spyvxwuoqtnx
Jan 2, 2026
Merged

Remove sparkle-cli (sparkle.app) from binary distribution#2826
zorgiepoo merged 1 commit into
2.xfrom
push-spyvxwuoqtnx

Conversation

@zorgiepoo

@zorgiepoo zorgiepoo commented Jan 2, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

External updater software usually (and often should) use SPUUpdater directly. sparkle-cli is a show case for this. Although the utility app is useful and software may want to rely on it, I think if they want to do that, they should also build/deploy with a custom PRODUCT_BUNDLE_IDENTIFIER that doesn't clash other client's usages.

Note this app is already not in the SPM distribution.

Misc Checklist

  • My change requires a documentation update on Sparkle's website repository
  • My change requires changes to generate_appcast, generate_keys, or sign_update

Testing

I tested and verified my change by using one or multiple of these methods:

  • Sparkle Test App
  • Unit Tests
  • My own app
  • Other (please specify)

Tested make release locally and verified sparkle.app is not in there.

macOS version tested: 26.2 (25C56)

@zorgiepoo zorgiepoo added this to the 2.9.0 milestone Jan 2, 2026
@zorgiepoo zorgiepoo merged commit 5e527f9 into 2.x Jan 2, 2026
2 checks passed
@zorgiepoo zorgiepoo deleted the push-spyvxwuoqtnx branch January 2, 2026 03:03
@sandermeis

sandermeis commented Mar 5, 2026 •
edited
Loading

Copy link
Copy Markdown

Unfortunately we relied on the external sparkle binary for updating our macos cli (cpp). Solved by installing xcode on our runners and building from source. Do you recommend that we now build this target ourselves instead of relying on a brew tap?

@zorgiepoo

zorgiepoo commented Mar 7, 2026 •
edited
Loading

Copy link
Copy Markdown
Member Author

Recommendations are what is described in the description of this PR + https://sparkle-project.org/documentation/sparkle-cli/ , namely to build sparkle-cli with a custom bundle identifier (not something we can distribute ourselves) so you don't clash with other folks using the tool, or to use Sparkle.framework directly if you are also distributing an app that also uses Sparkle for updating itself (thereby avoiding redundancy of bundling sparkle twice).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

2.9.0

Development

Successfully merging this pull request may close these issues.

2 participants

@zorgiepoo @sandermeis