GitLab

Seems is a flatpakishm that we support. Take a look at gnome-games
manifest.

So it doesn't break... seems people got used to use them.

When a manifest has a patch like
https://git.gnome.org/browse/gnome-photos/tree/flatpak/org.gnome.Photos.json#n13
the path is relative to the manifest.

However, we generate our own manifest from the original one for
developing purposes, so the path becomes different and the patch cannot
be found.

To fix it, we need to set the proper original path to the patch in the
generated manifest.

If the cache doesn't exist, then the function to remove it
breaks and causes the program to halt.

This patch checks to see if the cache exists before removing it.

This allows for easier debugging so that
old versions of the cache don't conflict.

This patch forces the cache to be removed before each execution.

The cache path makes more sense to be called
cache_path over dev_path.

This patch changes dev_path to cache_path

This change makes the cache ownership less ambiguous.

Change the cache from ~/.cache/flatpak-cli to ~/.cache/flatpak-dev

I was using configure instead of autogen.sh.

Like what the manifest does.

We wanted to use it for hacking on dependencies, but this is not a goal
right now and is confusing to have it.

So just remove it.

108403f4

 incorrectly assumes that enter-env.sh should be run from
setup-flatpak-dev.sh. The assumption is incorrect in that flatpak-dev.py
runs it as invoked from setup-flatpak-dev.sh.
Signed-off-by: Ernestas Kulik <ernestas.kulik@gmail.com>

setup-flatpak-dev.sh: run enter-env.sh instead of exporting PS1

Closes #1

See merge request !1

Currently, the script simply overwrites PS1, which is undesirable, since
a new shell is not started afterwards. enter-env.sh does it nicer, by
appending the old PS1 to the override and starting a new bash, which
also provides a more consistent experience, since the current script
preserves the current shell.

Fixes #1
Signed-off-by: Ernestas Kulik <ernestas.kulik@gmail.com>

This reverts commit 63817c4d