Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Snap package for Vencord #102

Closed
soumyaDghosh opened this issue Aug 27, 2023 · 10 comments
Closed

Snap package for Vencord #102

soumyaDghosh opened this issue Aug 27, 2023 · 10 comments

Comments

@soumyaDghosh
Copy link

I am creating a snap package for Vencord but can you suggest me the name, description and summary. I have thought about name as vencord but anything else is welcomed. The manifest is hosted here:

https://github.com/soumyaDghosh/vencord-snap

@TheKodeToad
Copy link
Contributor

TheKodeToad commented Aug 27, 2023

maybe you should ask on the Discord server?

@soumyaDghosh
Copy link
Author

Asked it, but the reply wasn't very good. Looked more like a spam.

@lewisakura
Copy link
Member

I think it'd be preferable if we distributed Vesktop ourselves on these platforms, but we're not interested in maintaining a Snap package at the minute.

@soumyaDghosh
Copy link
Author

@lewisakura should I publish the snap on my own then?

@lewisakura
Copy link
Member

We'd rather you didn't because people will come to us when it breaks and none of us will be able to provide support for it. Not just on GitHub, but on Discord too. People expect that when a package exists we will provide support for it, but in our case we don't have a clue how some of the unofficial repackages of Vencord work and we would rather do it ourselves in the future when we have a better understanding and there's more demand.

So, for the reasons above, please don't.

@soumyaDghosh
Copy link
Author

We'd rather you didn't because people will come to us when it breaks and none of us will be able to provide support for it. Not just on GitHub, but on Discord too. People expect that when a package exists we will provide support for it, but in our case we don't have a clue how some of the unofficial repackages of Vencord work and we would rather do it ourselves in the future when we have a better understanding and there's more demand.

So, for the reasons above, please don't.

As the snap will be simply a wrapper to the deb package. It'll not be something different. Also, snap is very immuted to these breakages, as I am seeing with webcord, another discord client.
SpacingBat3/WebCord#452

Snap one doesn't have this issue. All the other package formats have this. So, I think, it's better to have the snap. And also, I can maintain your snap if you want.

@Vendicated
Copy link
Member

Also, snap is very immuted to these breakages, as I am seeing with webcord, another discord client. Snap one doesn't have this issue.

This is simply not true. the issues you linked is native to electron itself, so it also occurs on snap unless the snap is an older version

In any case, we will be publishing our own official snap package. Please do not make your own.

@soumyaDghosh
Copy link
Author

Also, snap is very immuted to these breakages, as I am seeing with webcord, another discord client. Snap one doesn't have this issue.

This is simply not true. the issues you linked is native to electron itself, so it also occurs on snap unless the snap is an older version

Snap uses a stable version of electron and every other packages. That's why, I said it's very immutable.

@soumyaDghosh
Copy link
Author

Should I share the snap manifest with you guys? If you ever need them?

@0x3C50
Copy link

0x3C50 commented Oct 16, 2023

Should I share the snap manifest with you guys? If you ever need them?

The answer was clear enough. If need be for a snap package, I have good faith the vencord developers will be able to make their own snap setup they fully control.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants