2 Commits

Author	SHA1	Message	Date
Jonathan Lebon	cf07b45065	Makefile-hif.am: link by force and add clean hook ... Add a clean hook so that `make clean` on the top dir also cleans the libhif artifacts. Add -f to `ln` -- Make marks the target as out-of-date if the symlink breaks (which will happen if you just `make clean` in the libhif-build dir), but the `ln` will cause the build to fail since it already exists. Closes: #377 Approved by: cgwalters	2016-07-06 13:26:39 +00:00
Colin Walters	125c482b1d	Switch to using libhif as a git submodule ... So I was trying to hack on my host's copy of rpm-ostree inside a pet docker container, but ran into a conflict with libhif since dnf uses it. I think we basically need to *always* build the bundled path, rather than what I'm doing with CAHC and FADC where it's built as a regular RPM. It's not really sustainable right now for us to have both bundled and not-bundled build paths - and we need to support co-installation with dnf. Another major issue is that we want to version lock with libhif - right now our CI and both CAHC/FADC track libhif master, but that means everything breaks if libhif breaks and we don't immediately port. git submodules solve all of these problems - the same as we're doing with libglnx. libglnx is *designed* for use as a git submodule, where as libhif needs to support being both bundled and not-bundled. So we end up with some hacks on our side, but I think it's all not too bad. I've marked build rules with `# bundled libhif` so we know where to find them later when libhif is stable. Closes: #357 Approved by: jlebon	2016-06-30 14:27:55 +00:00