- 28 Jun, 2017 3 commits
-
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
Seems is a flatpakishm that we support. Take a look at gnome-games manifest.
-
Carlos Soriano Sánchez authored
So it doesn't break... seems people got used to use them.
-
- 27 Apr, 2017 4 commits
-
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
-
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.
-
- 25 Apr, 2017 1 commit
-
-
Carlos Soriano Sánchez authored
-
- 15 Apr, 2017 1 commit
-
-
Zack Lofgren authored
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.
-
- 14 Apr, 2017 4 commits
-
-
Zack Lofgren authored
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.
-
Zack Lofgren authored
The cache path makes more sense to be called cache_path over dev_path. This patch changes dev_path to cache_path
-
Zack Lofgren authored
This change makes the cache ownership less ambiguous. Change the cache from ~/.cache/flatpak-cli to ~/.cache/flatpak-dev
-
Carlos Soriano Sánchez authored
I was using configure instead of autogen.sh.
-
- 13 Apr, 2017 4 commits
-
-
Carlos Soriano Sánchez authored
Like what the manifest does.
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
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.
-
- 12 Apr, 2017 10 commits
-
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
-
Ernestas Kulik authored
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>
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
setup-flatpak-dev.sh: run enter-env.sh instead of exporting PS1 Closes #1 See merge request !1
-
Ernestas Kulik authored
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>
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
-
- 11 Apr, 2017 9 commits
-
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
This reverts commit 63817c4d
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
-
Carlos Soriano Sánchez authored
-