nautilus/build-aux/flatpak
Carlos Soriano d945455178 Flatpak: Separate master dependencies from stable
So far we have been building master of all of our dependencies, also
master of the Sdk. This is good for testing the next version of the
ecosystem, but has many downsides that we now can avoid with Flatpak.

For instance, we want to be buildable at any point in the history,
specially when doing bisects. Also, we need to be a bit stable so that
when designers, users or others build the latest Nautilus they are able
to work with it regardless of its dependencies on other projects.

Even more, now with CI we can test the master of the ecosystem regularly
while not affecting our regular development and operations by depending
on that.

So let's separate in two different manifests the development version
with stable dependencies, intended for our regular operations, and a
development version with all the ecosystem on master, to test the
ecosystem regularly on the CI or on-demand locally.
2018-05-28 19:50:08 +00:00
..
org.gnome.Nautilus-master.yml Flatpak: Separate master dependencies from stable 2018-05-28 19:50:08 +00:00
org.gnome.Nautilus.json Flatpak: Separate master dependencies from stable 2018-05-28 19:50:08 +00:00
org.gnome.Nautilus.yml Flatpak: Separate master dependencies from stable 2018-05-28 19:50:08 +00:00