Package Details: libquotient-git 0.6.0.r387.g7036ed0-1

Git Clone URL: (read-only, click to copy)
Package Base: libquotient-git
Description: A Qt5 library to write cross-platform clients for Matrix
Upstream URL:
Keywords: library matrix qt5 quotient
Licenses: LGPL2
Conflicts: libquotient
Provides: libquotient
Submitter: Scrumplex
Maintainer: aa13q
Last Packager: aa13q
Votes: 3
Popularity: 0.000004
First Submitted: 2019-07-15 19:56
Last Updated: 2020-04-30 19:35

Required by (4)

Sources (1)

Latest Comments

aa13q commented on 2020-04-08 22:01

Hello! Just FYI: libolm is not needed. Default cmake config is not searching for qtolm anymore while e2ee support is not ready: And when it will be ready it will be using qt5-olm library (a qt wrapper for olm)

morguldir commented on 2019-11-02 21:11

It's fixed now, but a couple of days ago quaternion's master was incompatible with libquotient's, so i went back to using a submodule. This will probably happen again and the quotient devs have said they won't give any guarantees that they won't break it.

morguldir commented on 2019-10-20 00:15

So it doesn't look like there are any plans to properly tag this thing, and i need to specify 0.6 for quaternion-git, so i wrote a new pkgver() function extracting the version out of CMakeFiles.txt. It should be pretty consistent.

pkgver() {
    cd "$pkgname"

    _info="$(git blame -s CMakeLists.txt | grep set\(API)"
    _commit="$(echo $_info | awk '{print $1}')"
    _ver="$(echo $_info | awk '{print $4}' | sed s/[^0-9.]//g)"
    _patch_ver="$(git blame -p CMakeLists.txt | grep project\(Quotient | sed s/[^0-9]//g)"
    _revisions="$(git rev-list --count $_commit..HEAD)"
    _current_commit="$(git log --pretty=format:'%h' -n 1)"
    printf "%s.%d.r%d.g%s" $_ver $_patch_ver $_revisions $_current_commit

Scrumplex commented on 2019-07-16 01:42

Thank you @Morguldir. Updated the package

morguldir commented on 2019-07-16 00:59

You should use -DBUILD_SHARED_LIBS=1 so that the package creates shared libraries instead.

Scrumplex commented on 2019-07-15 20:06

For some reason git thinks is the latest tag. I guess this will get fixed by time.