Package Details: kdeconnect-git 24.12.0+r4728+gf3c822e25-1

Git Clone URL: https://aur.archlinux.org/kdeconnect-git.git (read-only, click to copy)
Package Base: kdeconnect-git
Description: Adds communication between KDE and your smartphone
Upstream URL: https://kdeconnect.kde.org/
Licenses: GPL-2.0-or-later
Conflicts: kdeconnect
Provides: kdeconnect
Submitter: zizzfizzix
Maintainer: envolution
Last Packager: envolution
Votes: 158
Popularity: 0.000000
First Submitted: 2013-08-06 08:57 (UTC)
Last Updated: 2024-12-17 13:18 (UTC)

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 Next › Last »

amirs commented on 2013-09-08 13:41 (UTC)

moved to: git://anongit.kde.org/kdeconnect-kde

roentgen commented on 2013-09-02 18:33 (UTC)

Labell, that's the qdbus included in qt5 (the package qt5-tools). You can find what package has a file with pkgfile. Or if it's already installed with pacman -Qo file. I guess you can also use qdbus from qt4: /usr/lib/qt4/bin/qdbus or more straigh forward the symlink in /usr/bin qdbus-qt4

<deleted-account> commented on 2013-09-02 18:12 (UTC)

When I try to run the suggested commands after installing the packages I get the following error: [root@seb-desktop seb]# qdbus org.kde.kded /kded loadModule kdeconnect qdbus: could not exec '/usr/lib/qt/bin/qdbus': No such file or directory What did I miss?

ilpianista commented on 2013-08-24 13:06 (UTC)

1) IMHO every PKGBUILD should use Release. The developers know how to build packages with debug symbols. 2) yes, I mean double quotes. No, ${} isn't enough ;-)

zizzfizzix commented on 2013-08-23 13:37 (UTC)

Thanks for all the comments scarpino. I have two questions though: - Regarding debug option, should every package be built with Release then? Since without debug and/or !strip it doesn't make sense to set something else. - What do you mean by double apixes, double quotes? And if yes why is that so? I thought using ${} should guard against spaces and such. I did not set epoch since before you had to "downgrade" it anyway when updating

ilpianista commented on 2013-08-22 09:46 (UTC)

Also, you should use: echo $(git rev-list --count HEAD).$(git rev-parse --short HEAD) to generate the pkgver as described in the VCS PKGBUILD Guidelines wiki page

ilpianista commented on 2013-08-22 07:49 (UTC)

Some suggestion: - there is no need to put the install file in the source() array - keep the PKGBUILD KISS, there's no need to put the if statement to check the build type (also the 'debug' option is better then '!strip', as it creates a debug package too) - {srcdir}/{pkgdir} go between double apixes. Also each pkgver/package/build function change the dir to {srcdir} by default - please use a build dir, see the KDE_Packages_Guidelines wiki page.

zizzfizzix commented on 2013-08-20 11:23 (UTC)

From http://albertvaka.wordpress.com/2013/08/05/introducing-kde-connect/: "For battery reporting to work you will also need to apply this patch to kdelibs: solid-backend.patch"

SMOG commented on 2013-08-20 07:52 (UTC)

I think also avahi is no more necessary as dependence, as in his last post KDEConnect developer states: "More reliable connection backend, using broadcast messages instead of Avahi" http://albertvaka.wordpress.com/2013/08/10/kdeconnect-improvements/

SMOG commented on 2013-08-20 07:49 (UTC)

Hi everyone, I've installed KDEConnect on my phone (Android 4.0.3), my tablet (4.2.2) and on my laptop (Archlinux, KDE 4.11). Everything works fine, but one thing: battery applet integration. Do you guys are able to see battery status of your devices in KDE? Thanks :)

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 Next › Last »