[SailfishDevel] Harbour news

[Thomas Perl]

2013/12/19 Matt Austin <mail at mattaustin.me.uk>:
> On 18 December 2013 22:33, Thomas Perl <th.perl at gmail.com> wrote:
>> 2013/12/18  <dcaliste at free.fr>:
>>> - libxml2. As far as I know, their API is quite stable now even if it was not
>>> the case in the past (I remember having some trouble with it in 2003, but it's
>>> history now !).
>>
>> I've added it to the list of libs to be considered. Let's see...
>
> Do you think it likely that some python libraries are likely to be
> considered too?

At the moment, I think the best way is to ship any additional Python
libraries you need with your app (install somewhere below
/usr/share/$APPNAME/). I think it's much work to start pulling in
Python libraries into the repositories and difficult to maintain them
there.

Because of the dynamic nature of Python, it's even harder to verify
apps don't break with OS/library updates compared to native C/C++
libraries (where one could at least do a static check for exported
symbols, etc..). Just providing the standard library as shipped with
Python 3 is relatively easy to maintain, and apps can then ship
different versions of modules they need.

We can of course provide some guidelines for how to best
package/bundle Python libraries (especially more complicated ones that
involve C extension modules) into an application's RPM package, and
make sure the bundling/packaging experience is as good as possible.


HTH :)
Thomas