Runtime OSTree repository migration plan
After a discussion in the irc, we came agreed on the following structure of the repository.
I am not sure why the current setup in the Nightlies repository uses 2 different repositories,
one for the runtimes and one for the Applications. It worth investigating if we can use just 1 nightly repository
but since I don't know if there any blockers from doing so, here is the following plan which more or less
replicates the current setup of sdk.gnome.org
.
A repository for the Nightly builds
Meant to replace sdk.gnome.org/nightly/repo/
.
This will host the Nightly builds of the GNOME Runtime and replace the gnome-sdk-images.
A repository for the nightly GNOME applications.
Meant to replace sdk.gnome.org/nightly/repo-apps
. This will host the Nightly builds of the GNOME apps
and replace gnome-apps-nightly. Example gbm.g.o/nightly/repo-apps/
or gbm.g.o/nightly-apps/repo/
A repository for the builds needed to be exported for Flathub. gbm.g.o/import/repo/
Till flathub is able to build Buildstream projects, we will build and host the stable runtime builds there. This is not going to be the canonical way to distribute the GNOME Stable runetime. Do not pull from this repository directly, use Flathub instead.
Implementation plan
-
Setup a gbm.g.o/nightly/repo/
for the Nightlies builds of the runtime -
Setup a gbm.g.o/import/repo/
for the stable builds, ex. 3.30 -
Make a PR against flathub to import from gbm.g.o/import/repo/
#41 -
Stop building the Sdk/Platform from sdkbuilder1.g.org
andgnome1/gnome2.codethink.co.uk
. -
Configure sdk.gnome.org
to import the runtime fromgbm.gnome.org/nightly/repo
-
Build gnome apps with buildstream (See #45) -
Decommision sdk.g.o builders, sdkbuilder1.g.o and gnome1/2.codething.co.uk -
Alias gbm.gnome.org
toskd.gnome.org