VSCodium
Official Repo Releases
Hi, I hope you all are doing great.
VSCodium is here for a long time. I have been using it since I saw. You guys always packaging for different linux distros I also use your Fedora repo for installing and updating but why don't you publish binaries to official repositories. VSCodium is great and should be reachable by official repositories.
I'm planning to do:
- https://rpmfusion.org/
- https://copr.fedorainfracloud.org/
but never gave some time to do it.
I think eveybody uses rpmfusion. If you planning to give release please ignore copr and publish to rpm fusion. People should not need to add another repo for single app since VSCodium is not someone's weekend project. There are a lot of people who uses it.
I think eveybody uses rpmfusion. If you planning to give release please ignore copr and publish to rpm fusion. People should not need to add another repo for single app since VSCodium is not someone's weekend project. There are a lot of people who uses it.
copr would be better, because it is possible to download the .srpm and create builds for other distributions, besides Fedora. I use Mageia and could easily use copr, but not rpmfusion.
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!
@Tahinli I see following issues for packaging to official repos (numbered for further reference in comments) and why I've resigned to package my personal projects.
- Your app needs to be aligned exactly with the repository rules.
- You have to have runner with specific and updated version to build your app, which is costly.
- Guarding maintenance keys is a different story, because it's too easy to steal them.
Solutions for every point are welcome.
@Tahinli I see following issues for packaging to official repos (numbered for further reference in comments) and why I've resigned to package my personal projects.
- Your app needs to be aligned exactly with the repository rules.
- You have to have runner with specific and updated version to build your app, which is costly.
what are the runner details/type?
As for hosting. Oracle has a free tier that has a 4 core ARM CPU with 24GB RAM and 200GB HDD. Although ARM is the ARCH cross compilation can be used to achieve the desired ARCH(s). They also have an AMD VM avail too; although I don't know the details.
- Guarding maintenance keys is a different story, because it's too easy to steal them.
GH secrets could be used
Solutions for every point are welcome.
How much time CPU do they give for free tier?
this repo builds for about 30-60 minutes per build, there's about 10-15 popular distros, and many of them support few major versions.
If you'd like to target to repositories like AUR, you need just to repackage and add dependencies. If you'd like to target into at least "community" repository, clean build is highly preferred with external dependencies due to header includes. More so, in official repositories it's required to use existing packages, not fresh ones you've have in repo and tested for.
Snap repository is a good try, but the "sandbox" they require is quite harsh and even curl-snap is not recommended to use because '..' part in path is not allowed. The sandboxing on macOS works differently and an application may try to escape sandbox, but it won't.
GH secrets are relatively easy to steal. The small slipped change passed the review is enough.
How much time CPU do they give for free tier?
ref: https://www.oracle.com/au/cloud/free/
Arm-based Ampere A1 cores and 24 GB of memory usable as 1 VM or up to 4 VMs
Always Free 3,000 OCPU hours and 18,000 GB hours per month
so (~30 days a month x 24 hours a day = 720 hours month) * 4 CPU = 2880 hours if 4 CPUs used for whole month