shaba/ostree
1
0
Fork 0
mirror of https://github.com/ostreedev/ostree.git synced 2025-03-17 14:50:35 +03:00
Code Issues Projects Releases Wiki Activity
ostree/packaging/ostree.spec.in

123 lines
3.0 KiB
RPMSpec
Raw Permalink Normal View History

packaging: Update infrastructure The Makefile.dist-packaging lives canonically in rpm-ostree/ for now, it's my latest hack to automate git -> (s)rpm. Update the spec.in from current Fedora.
2014-01-18 04:44:54 -05:00
Summary: Git for operating system binaries
Name: ostree
Version: 2013.7
packaging: BR e2p
2014-06-21 16:55:36 -04:00
Release: 3%{?dist}
packaging: Update infrastructure The Makefile.dist-packaging lives canonically in rpm-ostree/ for now, it's my latest hack to automate git -> (s)rpm. Update the spec.in from current Fedora.
2014-01-18 04:44:54 -05:00
#VCS: git:git://git.gnome.org/ostree
Source0: http://ftp.gnome.org/pub/GNOME/sources/ostree/%{version}/ostree-%{version}.tar.xz
Source1: 91-ostree.preset
License: LGPLv2+
URL: http://live.gnome.org/OSTree
# We always run autogen.sh
BuildRequires: autoconf automake libtool
# For docs
BuildRequires: gtk-doc
# Core requirements
BuildRequires: pkgconfig(gio-unix-2.0)
BuildRequires: pkgconfig(libsoup-2.4)
packaging: BR libgsystem
2014-05-22 19:53:54 -04:00
BuildRequires: pkgconfig(libgsystem)
packaging: BR e2p
2014-06-21 16:55:36 -04:00
BuildRequires: pkgconfig(e2p)
packaging: Update infrastructure The Makefile.dist-packaging lives canonically in rpm-ostree/ for now, it's my latest hack to automate git -> (s)rpm. Update the spec.in from current Fedora.
2014-01-18 04:44:54 -05:00
# Extras
BuildRequires: pkgconfig(libarchive)
packaging: Add a fuse subpackage For rofiles-fuse. Eventually what we should really do is split out the shared library from the binaries? A minimal system shouldn't need rofiles-fuse, it's mainly for doing layered packages and that sort of thing.
2016-02-17 10:37:08 -05:00
BuildRequires: pkgconfig(fuse)
Add SELinux support The trees as shipped come with /usr/etc, which should just be labeled as usr_t. When we do a deployment, we need to relabel the copies of the files we're making in /etc. SELinux support is compile and runtime optional.
2014-01-29 09:22:16 -05:00
BuildRequires: pkgconfig(libselinux)
packaging: Sync spec file with Fedora
2016-02-03 10:22:01 -05:00
BuildRequires: libcap-devel
packaging: Update infrastructure The Makefile.dist-packaging lives canonically in rpm-ostree/ for now, it's my latest hack to automate git -> (s)rpm. Update the spec.in from current Fedora.
2014-01-18 04:44:54 -05:00
BuildRequires: gpgme-devel
BuildRequires: pkgconfig(systemd)
BuildRequires: /usr/bin/g-ir-scanner
BuildRequires: dracut
packaging: Sync spec file with Fedora
2016-02-03 10:22:01 -05:00
BuildRequires: bison
packaging: Update infrastructure The Makefile.dist-packaging lives canonically in rpm-ostree/ for now, it's my latest hack to automate git -> (s)rpm. Update the spec.in from current Fedora.
2014-01-18 04:44:54 -05:00
# Runtime requirements
Requires: dracut
Requires: systemd-units
%description
OSTree is a tool for managing bootable, immutable, versioned
filesystem trees. While it takes over some of the roles of tradtional
"package managers" like dpkg and rpm, it is not a package system; nor
is it a tool for managing full disk images. Instead, it sits between
those levels, offering a blend of the advantages (and disadvantages)
of both.
%package devel
Summary: Development headers for %{name}
Group: Development/Libraries
Requires: %{name} = %{version}-%{release}
%description devel
The %{name}-devel package includes the header files for the %{name} library.
libostree: Add initial GRUB2 support In this approach, we drop a /etc/grub.d/15_ostree file which is a hybrid of shell/C that picks up bits from the GRUB2 library (e.g. the block device script generation), and then calls into libostree's GRUB2 code which knows about the BLS entries. This is admittedly ugly. There exists another approach for GRUB2 to learn the BLS specification. However, the spec has a few issues: https://www.redhat.com/archives/anaconda-devel-list/2014-July/msg00002.html This approach also gives a bit more control to the admin via the naming of the 15_ostree symlink; they can easily disable it: Or reorder the ostree entries ahead of 10_linux: Also, this approach doesn't require patches for grub2, which is an issue with the pressure to backport (rpm-)OSTree to EL7.
2014-10-11 08:59:06 -04:00
%package grub2
Summary: GRUB2 integration for OSTree
Group: Development/Libraries
Requires: grub2
%description grub2
GRUB2 integration for OSTree
packaging: Add a fuse subpackage For rofiles-fuse. Eventually what we should really do is split out the shared library from the binaries? A minimal system shouldn't need rofiles-fuse, it's mainly for doing layered packages and that sort of thing.
2016-02-17 10:37:08 -05:00
%package fuse
Summary: FUSE utilities for OSTree
Group: Development/Libraries
Requires: fuse
%description fuse
%{summary}
packaging: Update infrastructure The Makefile.dist-packaging lives canonically in rpm-ostree/ for now, it's my latest hack to automate git -> (s)rpm. Update the spec.in from current Fedora.
2014-01-18 04:44:54 -05:00
%prep
%setup -q -n ostree-%{version}
%build
env NOCONFIGURE=1 ./autogen.sh
%configure --disable-silent-rules \
--enable-gtk-doc \
packaging: Update internal spec file
2014-03-01 15:46:03 -05:00
--with-selinux \
packaging: Update infrastructure The Makefile.dist-packaging lives canonically in rpm-ostree/ for now, it's my latest hack to automate git -> (s)rpm. Update the spec.in from current Fedora.
2014-01-18 04:44:54 -05:00
--with-dracut
make %{?_smp_mflags}
%install
make install DESTDIR=$RPM_BUILD_ROOT INSTALL="install -p -c"
find $RPM_BUILD_ROOT -name '*.la' -delete
install -D -m 0644 %{SOURCE1} $RPM_BUILD_ROOT/%{_prefix}/lib/systemd/system-preset/91-ostree.preset
%clean
rm -rf $RPM_BUILD_ROOT
%post
%systemd_post ostree-remount.service
%preun
%systemd_preun ostree-remount.service
%files
%doc COPYING README.md
%{_bindir}/ostree
%{_sbindir}/ostree-prepare-root
%{_sbindir}/ostree-remount
%{_sysconfdir}/dracut.conf.d/ostree.conf
%dir %{_prefix}/lib/dracut/modules.d/98ostree
%{_prefix}/lib/systemd/system/ostree*.service
%{_prefix}/lib/dracut/modules.d/98ostree/*
%{_libdir}/*.so.1*
%{_libdir}/girepository-1.0/OSTree-1.0.typelib
%{_mandir}/man1/*.gz
packaging: Add man5 pages
2015-02-03 20:28:18 -05:00
%{_mandir}/man5/*.gz
packaging: Update infrastructure The Makefile.dist-packaging lives canonically in rpm-ostree/ for now, it's my latest hack to automate git -> (s)rpm. Update the spec.in from current Fedora.
2014-01-18 04:44:54 -05:00
%{_prefix}/lib/systemd/system-preset/91-ostree.preset
packaging: Make the ostree rpm own and create /etc/ostree/remotes.d/
2014-08-02 18:09:52 -04:00
%dir %{_sysconfdir}/ostree/remotes.d
packaging: Update infrastructure The Makefile.dist-packaging lives canonically in rpm-ostree/ for now, it's my latest hack to automate git -> (s)rpm. Update the spec.in from current Fedora.
2014-01-18 04:44:54 -05:00
%files devel
%{_libdir}/lib*.so
%{_includedir}/*
%{_libdir}/pkgconfig/*
%{_datadir}/ostree
%dir %{_datadir}/gtk-doc/html/ostree
%{_datadir}/gtk-doc/html/ostree
%{_datadir}/gir-1.0/OSTree-1.0.gir
libostree: Add initial GRUB2 support In this approach, we drop a /etc/grub.d/15_ostree file which is a hybrid of shell/C that picks up bits from the GRUB2 library (e.g. the block device script generation), and then calls into libostree's GRUB2 code which knows about the BLS entries. This is admittedly ugly. There exists another approach for GRUB2 to learn the BLS specification. However, the spec has a few issues: https://www.redhat.com/archives/anaconda-devel-list/2014-July/msg00002.html This approach also gives a bit more control to the admin via the naming of the 15_ostree symlink; they can easily disable it: Or reorder the ostree entries ahead of 10_linux: Also, this approach doesn't require patches for grub2, which is an issue with the pressure to backport (rpm-)OSTree to EL7.
2014-10-11 08:59:06 -04:00
%files grub2
%{_sysconfdir}/grub.d/*ostree
%{_libexecdir}/ostree/grub2*
packaging: Add a fuse subpackage For rofiles-fuse. Eventually what we should really do is split out the shared library from the binaries? A minimal system shouldn't need rofiles-fuse, it's mainly for doing layered packages and that sort of thing.
2016-02-17 10:37:08 -05:00
%files fuse
%{_bindir}/rofiles-fuse
Reference in New Issue Copy Permalink