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
This card is about discussing a potential alternative to #1305.
#1305 originates from the needs of sandboxed builds.
Currently rancher/elemental#119 shifted framework static files to be consumed as a static assets, it also includes automatic PR creation to keep the framework up-to-date.
However, this way is very sub-optimal, and several alternatives have been considered, among using git submodules to track static framework files from a central place.
This card is explorative, and to try to assess what takes creating a specific OBS service for luet ( like https://en.opensuse.org/openSUSE:Build_Service_Concept_SourceService ) . The OBS service, could fetch assets remotely, like other services do ( e.g. git service, or python ) and treat luet like any other dependency management system ( e.g. npm, or alikes)
This card is about discussing a potential alternative to #1305.
#1305 originates from the needs of sandboxed builds.
Currently rancher/elemental#119 shifted framework static files to be consumed as a static assets, it also includes automatic PR creation to keep the framework up-to-date.
However, this way is very sub-optimal, and several alternatives have been considered, among using git submodules to track static framework files from a central place.
This card is explorative, and to try to assess what takes creating a specific OBS service for luet ( like https://en.opensuse.org/openSUSE:Build_Service_Concept_SourceService ) . The OBS service, could fetch assets remotely, like other services do ( e.g. git service, or python ) and treat
luet
like any other dependency management system ( e.g.npm
, or alikes)See also:
https://github.com/openSUSE/obs-service-github_tarballs
The text was updated successfully, but these errors were encountered: