keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
7b36814441
rpm-ostree/Makefile-rpm-ostree.am

81 lines
2.6 KiB
Plaintext
Raw Normal View History

Initial import from pkgsys-ostree
2013-12-22 04:41:30 +04:00
# Copyright (C) 2013 Colin Walters <walters@verbum.org>
#
# This library is free software; you can redistribute it and/or
# modify it under the terms of the GNU Lesser General Public
# License as published by the Free Software Foundation; either
# version 2 of the License, or (at your option) any later version.
#
# This library is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# Lesser General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public
# License along with this library; if not, write to the
# Free Software Foundation, Inc., 59 Temple Place - Suite 330,
# Boston, MA 02111-1307, USA.
Unify rpm-ostree into one binary And start making an internal library.
2014-01-29 23:37:44 +04:00
bin_PROGRAMS += rpm-ostree
Initial import from pkgsys-ostree
2013-12-22 04:41:30 +04:00
upgrade: Print out a summary of the package delta This requires us to link to hawkey.
2014-03-28 03:57:10 +04:00
noinst_LTLIBRARIES += librpmostree.la
librpmostree_la_SOURCES = \
Unify rpm-ostree into one binary And start making an internal library.
2014-01-29 23:37:44 +04:00
src/rpmostree-postprocess.c \
upgrade: Print out a summary of the package delta This requires us to link to hawkey.
2014-03-28 03:57:10 +04:00
src/rpmostree-postprocess.h \
compose: Split out JSON helpers into separate file In preparation for using some of them in the postprocessing code too. Yeah, parsing JSON in C sucks =( Oh well.
2014-11-13 22:53:43 +03:00
src/rpmostree-json-parsing.c \
src/rpmostree-json-parsing.h \
treecompose: Add initial caching The way this works is still fairly naive in that we hash in two inputs: 1) The treefile JSON 2) The result of rpm -qa If both of those are a hit, we reuse the existing commit.
2014-05-16 01:46:51 +04:00
src/rpmostree-util.c \
src/rpmostree-util.h \
compose: Introduce a little 'libcontainer', use it for the post script The current motivation for this is that https://github.com/fedora-infra/fedmsg-atomic-composer started using mock --new-chroot (which uses systemd-nspawn) to run rpm-ostree, which in turn uses systemd-nspawn to run the post script. Now systemd-nspawn is not really nestable (it wants to link up journald, resolv.conf handling, etc). First, dropping nspawn and going to raw containers fixes the nesting problem. Second, we don't need all the features of systemd-nspawn. We are ok with log messages going to stdout, and we don't use networking, so no resolv.conf is needed. Third, this sets a bit of a stage for more sandboxing internally when run on real systems. I already have a prototype branch which runs librepo as an unprivileged user, that could be combined with this for even stronger security. Why not use systemd? Well...I'm still debating that. But the core problem is systemd isn't a library in the C sense - to use its sandboxing features we have to use unit files. It's harder to have a daemon that looks like a single service from a management perspective, but uses sandboxing internally.
2014-11-20 02:30:00 +03:00
src/rpmostree-libcontainer.c \
src/rpmostree-libcontainer.h \
upgrade: Print out a summary of the package delta This requires us to link to hawkey.
2014-03-28 03:57:10 +04:00
src/hif-utils.c \
src/hif-utils.h \
Centralize cleanup function definitions We might as well do what systemd does and have a big header which defines all of them, to more conveniently share them for libraries that don't include them (like hawkey/librepo, as well as things that libgsystem doesn't yet cover).
2014-11-12 02:40:58 +03:00
src/rpmostree-cleanup.h \
upgrade: Download only /usr/share/rpm in check-diff This improves on the check-diff option by only downloading the /usr/share/rpm directory to do a package diff. This prevents downloading the whole deployment and the necessity to do a cleanup later.
2014-08-05 16:21:54 +04:00
src/rpmostree-treepkgdiff.c \
src/rpmostree-treepkgdiff.h \
Split up rpmostree-builtin-db.c As a followup to renaming the "rpm" command to "db", split the "db" subcommands into separate source files in the style of "ostree admin" and "rpm-ostree compose". Also create rpmostree-rpm-util.[ch] as a place for common rpm-related functions needed by the "db" subcommands. No intentional functional changes here, just a bunch of copy-n-paste and minor cleanup.
2014-12-02 01:38:42 +03:00
src/rpmostree-rpm-util.c \
src/rpmostree-rpm-util.h \
upgrade: Print out a summary of the package delta This requires us to link to hawkey.
2014-03-28 03:57:10 +04:00
$(NULL)
Put hawkey stuff behind --enable-patched-hawkey-and-libsolv Right now we depend on two patches.
2014-03-29 06:04:52 +04:00
if BUILDOPT_PATCHED_HAWKEY_AND_LIBSOLV
librpmostree_la_SOURCES += \
src/rpmostree-treepkgdiff.c \
src/rpmostree-treepkgdiff.h \
$(NULL)
endif
upgrade: Print out a summary of the package delta This requires us to link to hawkey.
2014-03-28 03:57:10 +04:00
librpmostree_la_CFLAGS = $(AM_CFLAGS) -I$(srcdir)/src -DPKGLIBDIR=\"$(pkglibdir)\" $(PKGDEP_RPMOSTREE_CFLAGS)
compose: Protect the system during treecompose using container APIs I was looking again at using hawkey/librepo, and realized just how much I'd have to fight all of these libraries to avoid affecting the running system. What we really want to do with librepo/hawkey is run them effectively unprivileged, and to hide the system's RPM database from them. This is a baby step towards that, by confining our existing yum. - /usr, /etc, and /var/lib/rpm are mounted read-only - yum is now run under CLONE_NEWPID, to avoid stray %post scripts affecting system processes
2014-11-10 04:28:10 +03:00
librpmostree_la_LIBADD = $(AM_LDFLAGS) $(PKGDEP_RPMOSTREE_LIBS) $(CAP_LIBS)
upgrade: Print out a summary of the package delta This requires us to link to hawkey.
2014-03-28 03:57:10 +04:00
rpm_ostree_SOURCES = src/main.c \
core: Use generic "builtin" infrastructure for command handling I want to have more options than just "create".
2014-03-22 23:05:41 +04:00
src/rpmostree-builtins.h \
Split up rpmostree-builtin-db.c As a followup to renaming the "rpm" command to "db", split the "db" subcommands into separate source files in the style of "ostree admin" and "rpm-ostree compose". Also create rpmostree-rpm-util.[ch] as a place for common rpm-related functions needed by the "db" subcommands. No intentional functional changes here, just a bunch of copy-n-paste and minor cleanup.
2014-12-02 01:38:42 +03:00
src/rpmostree-db-builtins.h \
Add upgrade builtin This is just the start of moving more functionality into rpm-ostree, with the goal of more tightly binding the rpm and ostree worldviews. For exmaple, supporting package installation on top, showing the package-level diff between trees, etc.
2014-03-25 02:11:21 +04:00
src/rpmostree-builtin-upgrade.c \
core: Add "rollback" builtin This is a convenient command to go back to the previous tree.
2014-03-29 03:48:06 +04:00
src/rpmostree-builtin-rollback.c \
Add a "rebase" builtin This is exactly the code from "ostree admin switch", except it's called "rebase" because in the future it will also carry along any locally layered packages.
2014-05-30 02:00:11 +04:00
src/rpmostree-builtin-rebase.c \
status: New builtin for system administrators to see deployments This allows administrators to configure between deployments and easily see which deployment they are booted into as well as indicating which is chronologically most recent. This makes the process more user-friendly, rather than requiring the user to remember which deployment checksum corresponds to the most recent upgrade.
2014-06-11 21:47:10 +04:00
src/rpmostree-builtin-status.c \
Rename "rpm" command to "db" Eliminates some confusion between "rpm-ostree rpm" (or "atomic rpm") commands versus actual "rpm" commands. The "rpm" subcommand is retained as a hidden alias for the "db" subcommand for backward-compatibility. It is not listed in --help output. Fixes #22
2014-12-02 01:38:08 +03:00
src/rpmostree-builtin-db.c \
Split up rpmostree-builtin-db.c As a followup to renaming the "rpm" command to "db", split the "db" subcommands into separate source files in the style of "ostree admin" and "rpm-ostree compose". Also create rpmostree-rpm-util.[ch] as a place for common rpm-related functions needed by the "db" subcommands. No intentional functional changes here, just a bunch of copy-n-paste and minor cleanup.
2014-12-02 01:38:42 +03:00
src/rpmostree-db-builtin-diff.c \
src/rpmostree-db-builtin-list.c \
src/rpmostree-db-builtin-version.c \
Add --disable-compose-tooling build option Some downstreams want the ability to separate the compose tooling from the client, for e.g. support reasons. This approach supports generating a tarball without the source for the compose command, and requires specifying a config option to disable it.
2014-09-17 05:45:30 +04:00
$(NULL)
if BUILDOPT_COMPOSE_TOOLING
rpm_ostree_SOURCES += \
Add new "compose" builtin, rename "treecompose" -> "compose tree" And do the same for "sign". This way we can have the compose server utilities cleanly separated from what most people will see, which is the client side tools.
2014-05-26 23:05:08 +04:00
src/rpmostree-compose-builtin-tree.c \
src/rpmostree-compose-builtin-sign.c \
Add --disable-compose-tooling build option Some downstreams want the ability to separate the compose tooling from the client, for e.g. support reasons. This approach supports generating a tarball without the source for the compose command, and requires specifying a config option to disable it.
2014-09-17 05:45:30 +04:00
src/rpmostree-builtin-compose.c \
Unify rpm-ostree into one binary And start making an internal library.
2014-01-29 23:37:44 +04:00
$(NULL)
Add --disable-compose-tooling build option Some downstreams want the ability to separate the compose tooling from the client, for e.g. support reasons. This approach supports generating a tarball without the source for the compose command, and requires specifying a config option to disable it.
2014-09-17 05:45:30 +04:00
endif
Use the now external libgsystem https://git.gnome.org/browse/libgsystem/commit/?id=9363cfc28ede912e2f06d4ccb42a646bb8a4bd2e
2014-02-08 02:29:40 +04:00
rpm_ostree_CFLAGS = $(AM_CFLAGS) -I$(srcdir)/src -DPKGLIBDIR=\"$(pkglibdir)\" $(PKGDEP_RPMOSTREE_CFLAGS)
upgrade: Print out a summary of the package delta This requires us to link to hawkey.
2014-03-28 03:57:10 +04:00
rpm_ostree_LDADD = $(AM_LDFLAGS) $(PKGDEP_RPMOSTREE_LIBS) librpmostree.la
Split out postprocess+commit to separate script As this logic is of most interest to potential other consumers; it's not entangled with yum for example.
2014-01-16 16:26:54 +04:00
Initial import from pkgsys-ostree
2013-12-22 04:41:30 +04:00
privdatadir=$(pkglibdir)
privdata_DATA = src/tmpfiles-ostree-integration.conf
build: Add --enable-usrbinatomic The name "rpm-ostree" kind of sucks; see: https://lists.projectatomic.io/projectatomic-archives/atomic/2014-April/msg00003.html But we can't make a hard transition easily, so let's add a build-time option to create an optional link for operating systems which want this.
2014-05-21 16:21:20 +04:00
if BUILDOPT_USRBINATOMIC
INSTALL_DATA_HOOKS += install-usrbinatomic-hook
install-usrbinatomic-hook:
build: Use ln -sf to help "sudo make install" This way we don't error when installing over an existing install.
2014-05-26 23:41:58 +04:00
ln -sf rpm-ostree $(DESTDIR)$(bindir)/atomic
ln -sf rpm-ostree.1.gz $(DESTDIR)$(mandir)/man1/atomic.1.gz
build: Add --enable-usrbinatomic The name "rpm-ostree" kind of sucks; see: https://lists.projectatomic.io/projectatomic-archives/atomic/2014-April/msg00003.html But we can't make a hard transition easily, so let's add a build-time option to create an optional link for operating systems which want this.
2014-05-21 16:21:20 +04:00
endif
Reference in New Issue Copy Permalink