Package Details: x11vnc-git 1:0.9.16.r12.g97d632c-1

Git Clone URL: https://aur.archlinux.org/x11vnc-git.git (read-only, click to copy)
Package Base: x11vnc-git
Description: VNC server for real X displays
Upstream URL: https://LibVNC.github.io
Licenses: GPL
Conflicts: x11vnc
Provides: x11vnc
Submitter: bidulock
Maintainer: bidulock
Last Packager: bidulock
Votes: 4
Popularity: 0.000000
First Submitted: 2014-09-22 04:28 (UTC)
Last Updated: 2019-10-01 06:02 (UTC)

Dependencies (15)

Required by (8)

Sources (2)

Latest Comments

FabioLolix commented on 2018-09-23 21:42 (UTC)

Would you like to use git describe --long --tags | sed 's/([^-]*-g)/r\1/;s/-/./g' as pkgver() since you reverted to the github repo?

bidulock commented on 2018-08-20 07:26 (UTC)

The major reason for using the fork was a seriously broken build system, which appears to be ok with recent commits. So, reverted back to using the upstream with included x11vnc.service file.

pmattern commented on 2015-10-26 22:01 (UTC)

Repo github.com/bbidulock/x11vnc hasn't been updated since more than a year, github.com/LibVNC/x11vnc from which it was forked is updated on a regular basis and apparently the one were the main development of x11vnc takes place right now. So I wonder whether it wouldn't make sense to use the latter for this package. Could of course very well be that there's a particular reason to use your bbidulock fork, e. g. some particular feature. But actually I think if so the feature in question should somehow be reflected in the corresponding AUR package's name while a package simply named x11vnc-git should rather provide some vanilla version of the main upstream repository which seems to be the LibVNC one as stated above atm.