Last week I created a post talking about the new project I’ve started on Github called “Terminate-Notice” (which in hindsight isn’t very accurate – at best it’s …
I can work on it. And try pushing just our config/addons/just type rpms. If that’s good, add the kmods , and if that’s all working good, start on negativo17.
Finally if all that is solid for us we can think about rpmfusion, but that’s a lot to bite off and definitely not plausible until the model is proven.
TLDR: He is building the packages using his source code through Github Action, making them available as a release, and then ingesting them into a repo that has a front end page available with Jekyll.
What amount of effort would it take to retool what we are doing in Copr and making it available in our Github Repo? OR another thought I just had is what if we just grab the RPMs directly from our sources we use and just mirror them?
In the second scenario, as long as we can grab the RPMs we need directly, we could just mirror them? Not really sure what the maximum amount of space you can store in a single Github Repo.
N
B
K
J
