Commit c43e26d4 authored by Sam Thursfield's avatar Sam Thursfield

Remove ref for tagcloud.bst

This references the repository that contains the file, it causes
an infinite loop if we try to store the ref of the commit containing
that file in the commit whose ref we need to store ...
parent 7c8285c2
......@@ -17,7 +17,8 @@ build_and_test:
# Update the ref in the project to build the correct branch. This is a bit
# ugly of course, but it saves turning the .bst file into a template.
- |
sed -e "s/ ref: .*/ ref: $CI_COMMIT_SHA/" -i flatpak/elements/tagcloud.bst
sed -e "/ track: .*/ a \\
ref: $CI_COMMIT_SHA" -i flatpak/elements/tagcloud.bst
# Build and install the app
......@@ -27,23 +27,6 @@ You can then run it with this command:
flatpak run
If you want a faster development loop, you can also install Tagcloud somewhere
into /opt. You will need to provide a manually fixed version of GObject
Introspection (see <>) and
an unreleased version GTK 3.22 that contains commit c9df0c34bf5 (see
<>). You can then do something
like this from the Tagcloud source tree:
mkdir build
cd build
meson .. -Dprefix=/opt/tagcloud
ninja install
You can then run Tagcloud like this:
env LD_LIBRARY_PATH=/opt/tagcloud/lib64 GI_TYPELIB_PATH=/opt/tagcloud/lib64/girepository-1.0:/opt/lib64/girepository-1.0 GIO_EXTRA_MODULES=/usr/lib64/gio/modules /opt/tagcloud/bin/tagcloud
Tracker domains
......@@ -8,7 +8,7 @@ OUTPUT_DIR="./tagcloud-flatpak"
FLATPAK="flatpak --user"
if [ -e "${OUTPUT_DIR}" ]; then
echo >&2 "ERROR: Output directory ${OUTPUT_DIR} already exists."
......@@ -13,6 +13,8 @@ depends:
type: all
- filename: python3-pyxdg.bst
type: all
- filename: tracker.bst
type: all
# DConf needs to be present inside the sandbox in order for trackerappdomain
# to function correctly. The Tracker daemons are run on a private session bus
......@@ -25,7 +27,6 @@ sources:
- kind: git
track: master
ref: foo
#- kind: local
# path: ../
......@@ -34,4 +35,4 @@ config:
# Perhaps Flatpak should take care of this for us?
- glib-compile-schemas %{install-root}/%{prefix}/share/glib-2.0/schemas
- glib-compile-schemas %{install-root}/%{prefix}/share/glib-2.0/schemas
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment