[PROPOSAL]: Snap package for ccextractor #790

Open
opened 2026-01-29 16:53:32 +00:00 by claunia · 7 comments
Owner

Originally created by @soumyaDghosh on GitHub (Dec 14, 2023).

I have created a snap package for the ccextractor. The main enhancement by this, is the fact that it can be used in any distro now, even if it's a non-LTS Ubuntu release, or an Arch based distro or anything else.

Also, if I can get some help in testing the package, that'd also be helpful.

Originally created by @soumyaDghosh on GitHub (Dec 14, 2023). I have created a snap package for the `ccextractor`. The main enhancement by this, is the fact that it can be used in any distro now, even if it's a non-LTS Ubuntu release, or an Arch based distro or anything else. Also, if I can get some help in testing the package, that'd also be helpful.
Author
Owner

@SparklinStar commented on GitHub (Jan 24, 2024):

I can help you with testing the package in Fedora 39.

@SparklinStar commented on GitHub (Jan 24, 2024): I can help you with testing the package in Fedora 39.
Author
Owner

@SP-XD commented on GitHub (Jan 26, 2024):

Create a appImage its better than a snap package

@SP-XD commented on GitHub (Jan 26, 2024): Create a appImage its better than a snap package
Author
Owner

@cfsmp3 commented on GitHub (Dec 28, 2025):

@soumyaDghosh Did you send a PR? What do you need from us?
In any case this should be, I suppose, a GitHub workflow that creates the snap package automatically as needed.

@cfsmp3 commented on GitHub (Dec 28, 2025): @soumyaDghosh Did you send a PR? What do you need from us? In any case this should be, I suppose, a GitHub workflow that creates the snap package automatically as needed.
Author
Owner

@Akki2005 commented on GitHub (Jan 6, 2026):

Hi, I’m interested in helping with this.

From the discussion, it sounds like the preferred direction would be:

  • an automated GitHub Actions workflow
  • that builds and publishes a Snap package
  • rather than a manually maintained Snap

Before proceeding, I wanted to confirm:

  1. Is Snap packaging still desired long-term?
  2. Should this target stable releases only, or every commit?
  3. Would a similar workflow for AppImage also be welcome, or should we focus on one format?

Happy to draft a proposal once direction is confirmed.

@Akki2005 commented on GitHub (Jan 6, 2026): Hi, I’m interested in helping with this. From the discussion, it sounds like the preferred direction would be: - an automated GitHub Actions workflow - that builds and publishes a Snap package - rather than a manually maintained Snap Before proceeding, I wanted to confirm: 1) Is Snap packaging still desired long-term? 2) Should this target stable releases only, or every commit? 3) Would a similar workflow for AppImage also be welcome, or should we focus on one format? Happy to draft a proposal once direction is confirmed.
Author
Owner

@x15sr71 commented on GitHub (Jan 8, 2026):

Hi all, just a quick follow-up on this proposal.

I’ve opened PR #1998, which implements Snap packaging for CCExtractor based on this discussion.
As suggested here, it’s done via a GitHub Actions workflow that builds the Snap automatically.

Thanks to @soumyaDghosh for the original proposal and to everyone who weighed in here.
If you have any thoughts or spot something worth adjusting, feel free to share, happy to iterate.

@x15sr71 commented on GitHub (Jan 8, 2026): Hi all, just a quick follow-up on this proposal. I’ve opened PR [#1998](https://github.com/CCExtractor/ccextractor/pull/1998), which implements Snap packaging for CCExtractor based on this discussion. As suggested here, it’s done via a GitHub Actions workflow that builds the Snap automatically. Thanks to @soumyaDghosh for the original proposal and to everyone who weighed in here. If you have any thoughts or spot something worth adjusting, feel free to share, happy to iterate.
Author
Owner

@soumyaDghosh commented on GitHub (Jan 8, 2026):

@x15sr71 Please refrain from submitting low-quality, LLM generated contributions that waste everyone's time.

@soumyaDghosh commented on GitHub (Jan 8, 2026): @x15sr71 Please refrain from submitting low-quality, LLM generated contributions that waste everyone's time.
Author
Owner

@x15sr71 commented on GitHub (Jan 8, 2026):

@x15sr71 Please refrain from submitting low-quality, LLM generated contributions that waste everyone's time.

@soumyaDghosh Thanks for the feedback.

I’m happy to address any specific technical concerns with the implementation, please feel free to point them out directly in the PR so they can be reviewed and improved if needed.

The goal here is to move the Snap proposal forward in line with maintainer guidance.

@x15sr71 commented on GitHub (Jan 8, 2026): > [@x15sr71](https://github.com/x15sr71) Please refrain from submitting low-quality, LLM generated contributions that waste everyone's time. @soumyaDghosh Thanks for the feedback. I’m happy to address any specific technical concerns with the implementation, please feel free to point them out directly in the PR so they can be reviewed and improved if needed. The goal here is to move the Snap proposal forward in line with maintainer guidance.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ccextractor#790