Hi all,

here are two very preliminary patches addressing an issue with python's 
easyinstall.

When installing python packages that are installed with python's easyinstall, 
the installation creates easyinstall.pth files. This file must exist in the 
root filesystem so that python 2.7 can locate and import the installed modules 
in the host system.

As I am still a novice writing recipes, I do not know the best practice to 
handle the issue above.
I have a first implementation that
  - uses a new class easyinstall
  - creates the easyinstall.pth if it did not exists or adds the entry in 
postinst script of the package
  - and requires the user to manually state what must be added

The related useradd recipe makes the impression that there are many further 
problems to think of that I am not aware of yet.
Is the postinst script of the package the correct place to write the 
easyinstall.pth file or is there possibly a better hook to use?

Probably, it would be best if what must be added is automatically extracted 
after the installation of the python module, and this routine is completely 
added to distutils class?

Undoubtedly the patch is only a very preliminary try addressing this issue with 
easyinstall.pth, but I wanted to get some feedback first.

Thank you for further help and advice.

Lukas


_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to