public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Owen W. Taylor <otaylor@fishsoup.net>
To: git-commits@fedoraproject.org
Subject: [flatpaks/flatpak-runtime] f45: Remove unused flatpak-runtime-packages.yaml
Date: Fri, 11 Sep 2026 14:40:15 GMT [thread overview]
Message-ID: <178913761573.1.15373376168560202317.flatpaks-flatpak-runtime-ff8598231fa4@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : flatpaks/flatpak-runtime
Branch : f45
Commit : ff8598231fa44525981b80e79970b9ba7f69ddaf
Author : Owen W. Taylor <otaylor@fishsoup.net>
Date : 2018-01-31T11:21:56+01:00
Stats : +0/-87 in 1 file(s)
URL : https://src.fedoraproject.org/flatpaks/flatpak-runtime/c/ff8598231fa44525981b80e79970b9ba7f69ddaf?branch=f45
Log:
Remove unused flatpak-runtime-packages.yaml
---
diff --git a/flatpak-runtime-packages.yaml b/flatpak-runtime-packages.yaml
deleted file mode 100644
index 83b0237..0000000
--- a/flatpak-runtime-packages.yaml
+++ /dev/null
@@ -1,87 +0,0 @@
-# This is a set of binary packages that we should depsolve to get the
-# set of packages that are installed into the runtime.
-runtime-roots:
- - enchant
- - hunspell-en-US
- - hunspell-en-GB
- - gtk3
- - gnome-desktop3
- - gvfs-client
- - librsvg2
- - libappstream-glib
- - python3-gobject
- - zenity
-
-# These are extra packages to install into the runtime beyond what we
-# depsolve from runtime-roots.
-extra-runtime-packages:
- - flatpak-runtime-config
-
-# These are the extra packages that we want available as build dependencies
-# for application modules. -devel packages are listed explicitly, because
-# we need to make sure they are installable and potentially build more
-# packages. For example, 'gobject-introspection' is part of base-runtime,
-# but base-runtime doesn't include all the python packages that
-# the tools in gobject-introspection-devel need.
-builddep-roots:
- - gtk3-devel
- - gnome-desktop3-devel
- - librsvg2-devel
- - libappstream-glib-devel
- - intltool
- - itstool
- - gobject-introspection-devel
- - pygobject3-devel
-
-# These are extra components to include literally in the component list;
-# they are listed here either because they aren't in F26, so can't be
-# depsolved, or because they are in a module we depend upon, but we need
-# to rebuild them explicitly for some reason
-extra-components:
- flatpak-rpm-macros:
- rationale: Set up build root for flatpak RPMS
- ref: master
- flatpak-runtime-config:
- rationale: Runtime configuration files
- ref: master
- glib2:
- rationale: Rebuild to fix triggers
- ref: private-f26-flatpak
- buildorder: -1
- gobject-introspection:
- rationale: >
- Rebuild to include devel which is filtered out of base-runtime
- ref: f26
- buildorder: 0
-
-# These are binary packages built from extra-components that we want
-# in the api list
-extra-api:
- - flatpak-rpm-macros
- - flatpak-runtime-config
- - glib2
- - glib2-devel
- - gobject-introspection
- - gobject-introspection-devel
-
-# These are keys to change for packages that we do depsolve
-overrides:
- python-cryptography:
- # Freeze to this version, until python-cryptography 1.9 is in
- # updates-testing and the bootstrap module is updated as well
- # otherwise we fail on missing/ wrong-versioned dependencies.
- ref: e0298e25e9da5501076d61449640f61c10fdef5a
-
-# When computing the order to build things in, we can get into circular
-# dependencies
-# For example gtk3 requires wayland which requires dot from graphviz
-# to build, but graphviz needs gtk3. The packages in this list indicate
-# links to ignore when computing the build order.
-build-order-ignore:
- - adwaita-icon-theme
- - graphviz
- - python-sphinx
- - python2-sphinx
- - gtk-update-icon-cache
- - python2-setuptools
- - python3-setuptools
reply other threads:[~2026-09-11 14:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178913761573.1.15373376168560202317.flatpaks-flatpak-runtime-ff8598231fa4@fedoraproject.org \
--to=otaylor@fishsoup.net \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox