Re: [Opensync-devel] python site-packages, debian, and opensync

[Bjoern R. <bjo...@go...>]

Hi Chris,

Am 05.07.11 23:16, schrieb Chris Frey:
> True, it is debian specific, and it would be nice to have this in the
> binary packaging.  But as far as I know, the new module won't
> work if I put it all by itself in an empty site-packages on Debian.
> It seems silly to go with site-packages, if I can get the real directory
> from python, like I'm doing now.
The official python way is to use site-packages. Therefore we should use
that directory too. They best way is to add a cmake variable to be able
to change the install dir via commandline. If not Debian could also add
a short and easy patch to use dist-packages.
> In reading docs.python.org, the "upstream method" is to use a setup.py to
> install and rely on Python's distutils.  But my patch is already using
> distutils (programmatically) to find the lib directory.  I'm not sure
> it is worth adding a setup.py for the opensync wrapper.  It would make
> it more official, I suppose.
Distutils aren't nice to handle for building libraries. Imho it lacks of
dependency management. Personally I did replace a setup.py installation
with cmake and it works much better then before. Therefore I would also
go for cmake instead of distutils.

Regards,
Björn