[Rpm-ecosystem] libhif, and grand plans

Neal Gompa ngompa13 at gmail.com
Fri Jul 24 16:17:04 UTC 2015

On Fri, Jul 24, 2015 at 10:37 AM, Richard Hughes <hughsient at gmail.com>

> On 24 July 2015 at 15:07, Neal Gompa <ngompa13 at gmail.com> wrote:
> > If the interfaces are cleanly available (such that applicable libraries
> can
> > be used in non-RPM systems as desired)
> You want to be able to use hawkey for non-rpm systems? I wasn't going
> to support the complexity of that use case without good reason.
​Well, I'm looking into building a tool along the lines of mock that uses
debbuild <https://secure.deepnet.cx/trac/debbuild>​ to generate Debian
packages, using hawkey to do the dependency solving for build dependencies.
The tool is going to be part of a greater system for me to have a
lightweight builder system for building DEB/RPM packages from common
sources. On the RPM side, there's mock for Fedora and I'm still trying to
work out how I'm going to do it for SUSE and Mageia. The Debian side
doesn't really have anything applicable to my needs, so I know I've got to
build it up.

> > and everything (including libhif) is
> > using CMake (which makes it much easier to integrate into other
> projects),
> Can you elaborate why cmake makes it easier than just shipping a
> pkgconfig file? The build system of the used library should make no
> effect on the consuming project.

​pkgconfig is only useful if the libraries are built and available on the
system. If they are not, having libhif, hawkey, librepo, *et al* using
​CMake means I can import the CMakeLists and just have it build for me
without a lot of crazy work. I've been using CMake for the vast majority of
my private projects, and all of my public projects that do require building
do use CMake. Of course, I could do custom build steps and call out to
autotools, but frankly I would prefer it if it all lived within CMake's own
world, because then the build process and targets are globally tracked.

As it is, all of libhif's dependent libraries use CMake *now*, so frankly
it makes little sense to autotoolize them when converting the libhif
buildsystem to CMake would allow the deeper integration you seek.

> Richard
> _______________________________________________
> Rpm-ecosystem mailing list
> Rpm-ecosystem at lists.rpm.org
> http://lists.rpm.org/mailman/listinfo/rpm-ecosystem

真実はいつも一つ!/ Always, there's only one truth!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-ecosystem/attachments/20150724/2f070fb1/attachment.html>

More information about the Rpm-ecosystem mailing list