rpms/flatpak-xdg-utils
7
0
Fork 0
Code Issues Pull Requests Releases Activity
2fac2ac095
flatpak-xdg-utils/flatpak-xdg-utils.spec

64 lines
1.8 KiB
RPMSpec
Raw Normal View History

Initial import
2019-01-18 15:25:07 +00:00
Name: flatpak-xdg-utils
Summary: Command-line tools for use inside Flatpak sandboxes
Version: 1.0.0
Fix the name of the new subpackage to actually be flatpak-spawn
2019-09-15 16:00:20 +00:00
Release: 5%{?dist}
Initial import
2019-01-18 15:25:07 +00:00
License: LGPLv2+
URL: https://github.com/flatpak/flatpak-xdg-utils
Source: https://github.com/flatpak/%{name}/releases/download/%{version}/%{name}-%{version}.tar.xz
BuildRequires: gcc
BuildRequires: meson
BuildRequires: pkgconfig(glib-2.0)
Split flatpak-spawn into a separate sub-package The org.freedesktop.Flatpak user D-Bus service isn't just used by flatpak(1) or applications running as Flatpaks. It's also used by toolbox(1) for similar reasons: * To keep various configuration files inside the container synchronized with the host * To let the container request certain commands to be run on the host Unfortunately, the utilities other than flatpak-spawn (ie., xdg-email and xdg-email) that are meant to replace their counterparts in the xdg-utils package don't work inside Toolbox containers [1]. Moreover, there are RPM packages out there (eg., google-chrome) that "Require" xdg-utils. This causes conflicts if flatpak-xdg-utils is installed. Since Toolbox only needs flatpak-spawn to be present inside a container, there's no need to pull in the other utilities in the first place. It's a simple way to step around the above problems. [1] https://github.com/flatpak/xdg-desktop-portal/pull/348
2019-09-13 15:48:18 +00:00
Requires: flatpak-spawn%{?_isa} = %{?epoch:%{epoch}:}%{version}-%{release}
Initial import
2019-01-18 15:25:07 +00:00
%description
This package contains a number of command-line utilities for use inside
Flatpak sandboxes. They work by talking to portals.
Fix the name of the new subpackage to actually be flatpak-spawn
2019-09-15 16:00:20 +00:00
%package -n flatpak-spawn
Summary: Command-line frontend for the org.freedesktop.Flatpak service
License: LGPLv2+
Conflicts: flatpak-xdg-utils < 1.0.0-4
Split flatpak-spawn into a separate sub-package The org.freedesktop.Flatpak user D-Bus service isn't just used by flatpak(1) or applications running as Flatpaks. It's also used by toolbox(1) for similar reasons: * To keep various configuration files inside the container synchronized with the host * To let the container request certain commands to be run on the host Unfortunately, the utilities other than flatpak-spawn (ie., xdg-email and xdg-email) that are meant to replace their counterparts in the xdg-utils package don't work inside Toolbox containers [1]. Moreover, there are RPM packages out there (eg., google-chrome) that "Require" xdg-utils. This causes conflicts if flatpak-xdg-utils is installed. Since Toolbox only needs flatpak-spawn to be present inside a container, there's no need to pull in the other utilities in the first place. It's a simple way to step around the above problems. [1] https://github.com/flatpak/xdg-desktop-portal/pull/348
2019-09-13 15:48:18 +00:00
Fix the name of the new subpackage to actually be flatpak-spawn
2019-09-15 16:00:20 +00:00
%description -n flatpak-spawn
Split flatpak-spawn into a separate sub-package The org.freedesktop.Flatpak user D-Bus service isn't just used by flatpak(1) or applications running as Flatpaks. It's also used by toolbox(1) for similar reasons: * To keep various configuration files inside the container synchronized with the host * To let the container request certain commands to be run on the host Unfortunately, the utilities other than flatpak-spawn (ie., xdg-email and xdg-email) that are meant to replace their counterparts in the xdg-utils package don't work inside Toolbox containers [1]. Moreover, there are RPM packages out there (eg., google-chrome) that "Require" xdg-utils. This causes conflicts if flatpak-xdg-utils is installed. Since Toolbox only needs flatpak-spawn to be present inside a container, there's no need to pull in the other utilities in the first place. It's a simple way to step around the above problems. [1] https://github.com/flatpak/xdg-desktop-portal/pull/348
2019-09-13 15:48:18 +00:00
This package contains the flatpak-spawn command-line utility. It can be
used to talk to the org.freedesktop.Flatpak service to spawn new sandboxes,
run commands on the host, or use one of the session or system helpers.
Initial import
2019-01-18 15:25:07 +00:00
%prep
%autosetup
%build
%meson
%meson_build
%install
%meson_install
%files
%doc README.md
%license COPYING
Split flatpak-spawn into a separate sub-package The org.freedesktop.Flatpak user D-Bus service isn't just used by flatpak(1) or applications running as Flatpaks. It's also used by toolbox(1) for similar reasons: * To keep various configuration files inside the container synchronized with the host * To let the container request certain commands to be run on the host Unfortunately, the utilities other than flatpak-spawn (ie., xdg-email and xdg-email) that are meant to replace their counterparts in the xdg-utils package don't work inside Toolbox containers [1]. Moreover, there are RPM packages out there (eg., google-chrome) that "Require" xdg-utils. This causes conflicts if flatpak-xdg-utils is installed. Since Toolbox only needs flatpak-spawn to be present inside a container, there's no need to pull in the other utilities in the first place. It's a simple way to step around the above problems. [1] https://github.com/flatpak/xdg-desktop-portal/pull/348
2019-09-13 15:48:18 +00:00
%{_bindir}/xdg-email
%{_bindir}/xdg-open
Initial import
2019-01-18 15:25:07 +00:00
Fix the name of the new subpackage to actually be flatpak-spawn
2019-09-15 16:00:20 +00:00
%files -n flatpak-spawn
Split flatpak-spawn into a separate sub-package The org.freedesktop.Flatpak user D-Bus service isn't just used by flatpak(1) or applications running as Flatpaks. It's also used by toolbox(1) for similar reasons: * To keep various configuration files inside the container synchronized with the host * To let the container request certain commands to be run on the host Unfortunately, the utilities other than flatpak-spawn (ie., xdg-email and xdg-email) that are meant to replace their counterparts in the xdg-utils package don't work inside Toolbox containers [1]. Moreover, there are RPM packages out there (eg., google-chrome) that "Require" xdg-utils. This causes conflicts if flatpak-xdg-utils is installed. Since Toolbox only needs flatpak-spawn to be present inside a container, there's no need to pull in the other utilities in the first place. It's a simple way to step around the above problems. [1] https://github.com/flatpak/xdg-desktop-portal/pull/348
2019-09-13 15:48:18 +00:00
%license COPYING
%{_bindir}/flatpak-spawn
Initial import
2019-01-18 15:25:07 +00:00
%changelog
Fix the name of the new subpackage to actually be flatpak-spawn
2019-09-15 16:00:20 +00:00
* Sun Sep 15 2019 Kalev Lember <klember@redhat.com> - 1.0.0-5
- Fix the name of the new subpackage to actually be flatpak-spawn
Split flatpak-spawn into a separate sub-package The org.freedesktop.Flatpak user D-Bus service isn't just used by flatpak(1) or applications running as Flatpaks. It's also used by toolbox(1) for similar reasons: * To keep various configuration files inside the container synchronized with the host * To let the container request certain commands to be run on the host Unfortunately, the utilities other than flatpak-spawn (ie., xdg-email and xdg-email) that are meant to replace their counterparts in the xdg-utils package don't work inside Toolbox containers [1]. Moreover, there are RPM packages out there (eg., google-chrome) that "Require" xdg-utils. This causes conflicts if flatpak-xdg-utils is installed. Since Toolbox only needs flatpak-spawn to be present inside a container, there's no need to pull in the other utilities in the first place. It's a simple way to step around the above problems. [1] https://github.com/flatpak/xdg-desktop-portal/pull/348
2019-09-13 15:48:18 +00:00
* Fri Sep 13 2019 Debarshi Ray <rishi@fedoraproject.org> - 1.0.0-4
- Split flatpak-spawn into a separate sub-package
- Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild Signed-off-by: Fedora Release Engineering <releng@fedoraproject.org>
2019-07-25 00:41:21 +00:00
* Thu Jul 25 2019 Fedora Release Engineering <releng@fedoraproject.org> - 1.0.0-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild Signed-off-by: Fedora Release Engineering <releng@fedoraproject.org>
2019-01-31 19:49:03 +00:00
* Thu Jan 31 2019 Fedora Release Engineering <releng@fedoraproject.org> - 1.0.0-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
Initial import
2019-01-18 15:25:07 +00:00
* Wed Jan 16 2019 Owen Taylor <otaylor@redhat.com> - 1.0.0-1
- Initial version
Reference in New Issue Copy Permalink