Comment 3 for bug 1012703

Dear Sebastian.

On 13/06/12 16:17, Sebastian Heinlein wrote:
> You also need to patch the build system. It currently only supports
> building one Python version at the same time.
>

Can you please elaborate?

There are no extensions build, yet the autoconf detects libs/cflags/etc
hence it feels like there is a python extension module somewhere. The
pure python module is installed by the upstream build system as is from
lib/python/packagekit/ as is into correct dist-packages location using
automake rules.

Also note that python-packagekit is Arch:all package.

The enums.py is generated, but shipped in the tarball.

At first I did do automake out-of-tree builds with all python2s and
python3s in separate build directories. Only to realise, that actually
this is not required...

From my point I actually see no evidence of 'building' done by the build
system, apart from generating enums.py

> I took a short look at porting to Python3 for aptdaemon, since we
> re-use the packagekit.enums module. But I decided to just ship the enums
> in aptdaemon and to drop the python-packagekit dependency.
>

python3 support was done by upstream, only packaging is required.

Or did I miss something?

Regards,
Dmitrijs

--
Regards,
Dmitrijs.