You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More than an issue, I just wanted to share how I made a multi-package flatpak remote source using this project as base.
First I created a repo that would work as a hub for all the other projects [0]. This repository has a folder with all of the OCI descriptions from github and a workflow that mixes them and creates the file to host on gh-pages.
On each of the source projects, I created a workflow that builds the flatpak OCI image for the project [1], then it pushes them to the github OCI repo the same way this project does [2]. Then, instead of updating the local gh-pages branch of the project, I send a commit to update it's respective OCI description file on the hub repo [3].
For all of this to work I also had to create and install the respective keys for the projects to push the packages into the OCI repository and to update the description files into the hub repo... but I won't go into details about this process here.
I thought on upstreaming this workflow, but it didn't made sense since I changed the structure of the project a lot for this to work. I hope that at the very least this helps :)
More than an issue, I just wanted to share how I made a multi-package flatpak remote source using this project as base.
First I created a repo that would work as a hub for all the other projects [0]. This repository has a folder with all of the OCI descriptions from github and a workflow that mixes them and creates the file to host on gh-pages.
On each of the source projects, I created a workflow that builds the flatpak OCI image for the project [1], then it pushes them to the github OCI repo the same way this project does [2]. Then, instead of updating the local gh-pages branch of the project, I send a commit to update it's respective OCI description file on the hub repo [3].
For all of this to work I also had to create and install the respective keys for the projects to push the packages into the OCI repository and to update the description files into the hub repo... but I won't go into details about this process here.
I thought on upstreaming this workflow, but it didn't made sense since I changed the structure of the project a lot for this to work. I hope that at the very least this helps :)
[0] https://github.com/grillo-delmal/inochi2d-flatpak-devtest
[1] https://github.com/gasinvein/proton-flatpak/blob/master/.github/workflows/flatpak.yml#L18-L70
[2] https://github.com/gasinvein/proton-flatpak/blob/master/.github/workflows/flatpak.yml#L102-L132
[3] https://github.com/gasinvein/proton-flatpak/blob/master/.github/workflows/flatpak.yml#L134-L186
The text was updated successfully, but these errors were encountered: