[egenix-users] pyrun -- adding libraries

[M.-A. Lemburg]

On 04.02.2013 15:48, John R. Frank wrote:
>>>>> My goal is use pyrun to deploy a python program that depends on the lxml python module, which
>>>>> needs libxslt.so.1, libexslt.so.0, libxml2.so.2
>>>>>
>>>>> These are available on my Ubuntu build system from the debian packages libxml2 and libxslt --
>>>>> and I could rebuild them from source. How does one get PyRun to incorporate such additional
>>>>> libraries, so I can then deploy pyrun (and our custom program) to other machines that do not
>>>>> have any of these libraries?
>>>>
>>>> Additional libraries can be included in pyrun, but only if the libs can be statically linked and
>>>> the Python extensions interfacing to them support static linking as well.
>>>>
>>>> One of the things we'd like to do is make the configuration of such things easier. At the
>>>> moment, this requires digging deep into the way the pyrun is built.
>>>>
>>>> You have to add a corresponding section for the Python extension to Runtime/Setup.PyRun-2.7 and
>>>> the include_list in Runtime/makepyrun.py
>>>
>>>
>>> I don't see "Runtime" in the stuff downloaded by install-pyrun, and while the web page [1]
>>> mentions a source tarball, I cannot find a link to download a source archive for pyrun.  Am I
>>> missing it on that page?
>>
>> The Runtime/ dir is part of the source tarball. It is not included in the binary archives that
>> install-pyrun fetches from our site.
>>
>> Please see the download section for the download link:
>>
>> http://www.egenix.com/products/python/PyRun/#Download
> 
> 
> Found it, thanks!  Reading it.
> 
> Strategy question:  what do you see as the advantages or differences between building PyRun-based
> deploy and building a chroot containing python and all our dependencies using something like
> deboostrap [1]?

For us, the main motivation for pyrun was to be able to easily ship
a pre-configured Python run-time to the user, without having to worry
about incompatibilities of different OS Python installations or
making the installation process itself difficult for the user.

A chroot environment would allow separating the Python installation
from the rest of the system (and in a way that goes far beyond of
what pyrun can do), but also needs a more complicated setup on the
user system.

> Thanks for your expertise on this.
> 
> Regards,
> John
> 
> 
> 
> [1] -  https://wiki.ubuntu.com/DebootstrapChroot

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Feb 04 2013)
>>> Python Projects, Consulting and Support ...   http://www.egenix.com/
>>> mxODBC.Zope/Plone.Database.Adapter ...       http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________

::::: Try our mxODBC.Connect Python Database Interface for free ! ::::::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/