Re: [orca-list] Pluginsystem for Orca using libpeas



Hi,

I would go for: 3. Build libpeas from source.

Make a package for it just took 40 seconds on my laptop.

I'll leave for others to tell you how to do that for Ubuntu.

Cheers,
Didier


Le 10/06/2021 à 18:44, Geoff Shang a écrit :
On Thu, 10 Jun 2021, chrys wrote:

if this commit is true, you need at least version 1.26 of libpeas from January 2020.

Debian Bullseye (the next release) has libpeas 1.28.

Unfortunately, it doesn't appear to be in buster-backports.

I looked at the version in Bullseye. It actually has fewer dependencies than the version in Buster, and many of them are the same version or are covered by packages in Buster.

However, it depends on libpython3.9, and as the version of Python in Buster is 3.7.3 and one of the dependencies for libpython3.9 is libc6 >= 2.29 which is higher than the version in Buster, trying to pull in libpeas from Bullseye will result in an upgrade of libc6 which will suck in a whole lot of other packages.

As I see it, your choices are:

1.  Upgrade to Bullseye.  Bullseye is currently frozen and is likely to release soon, so this might be safe enough to do.  I'm going to do this on one of my systems for a similar reason - I need Python > 3.7.  You should read the release notes first though as there may be important changes (you should do this anyway).

2.  Pull in libpeas from Bullseye anyway and accept all the upgraded packages.  This will result in a partially upgraded system which is probably not a good idea, especially given that lib6 will be upgraded.

3.  Build libpeas from source. I have no idea at all how involved this is and it may well be more work than it's worth, particularly given the dependencies.

4.  Wait for Bullseye to release.

HTH,
Geoff.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]