[packagekit] Ipkg backend performance (and heads up for configure)

Richard Hughes hughsient at gmail.com
Thu Jan 24 11:10:03 PST 2008

On Thu, 2008-01-24 at 11:30 +0800, Tick wrote:
> pk-backend-apt.c:27:31: error: pk-backend-python.h: No such file or 
> directory

Well, I've done two things here:

* Fixed up the apt backend like the others so it compiles
* Fixed up the configure check so you only build what you really want

This means my configure line now is:

./configure --prefix=/home/hughsie/.root --enable-tests \
--enable-gtk-doc --enable-local --enable-yum --enable-apt \
--with-apt-search=plain --with-default-backend=yum

This means I can configure, build and test more than one backend, just
like I can with the waf build system.

So, for opkg testing you probably want to compile with:

./configure --prefix=/tmp --enable-opkg --with-default-backend=opkg

I hope that helps,


p.s. if you are building rpm's, you'll probably have to add this to the
spec file so the right stuff gets built.

More information about the PackageKit mailing list