[packagekit] [PATCH 1/1] alpm: bump required libalpm version to 9.0.0

[Matthias Klumpp]

2014-12-30 23:13 GMT+01:00 Richard Hughes <hughsient at gmail.com>:
> On 28 December 2014 at 18:51, Christian Hesse <list at eworm.de> wrote:
>> This bumps required libalpm version number to 9.0.0. Please note that we
>> have to check libalpm version, not pacman version!
>
> I'm getting very confused with what patch to apply for libalpm
> backend; can you please comment on
> https://github.com/hughsie/PackageKit/pull/26 and come up with a patch
> that everyone agrees on please. Thanks.
>
> I'm also not super happy with the way libalpm is playing
> fast-and-loose with versioning and sonames. It's going to make it hard
> considering that PackageKit has stable branches and only releases
> every couple of months.

I agree that the libalpm situation is not really ideal. But is this a
concern for us at PackageKit? IMHO this should be dealt with by the
one maintaining PK for Arch, so the alpm backend and libalpm match.
Any patches can be included in PK.
Given the nature of Arch as rolling-release, they might not even be
interested in the PK stable series at all, and just ship with the
latest PK version.
In general, not an ideal situation, but also not a serious problem for
PackageKit or the inclusion/maintenance of the alpm backend - or am I
missing something here?
Cheers,
    Matthias