Search Criteria
Package Details: x11vnc-git 0.9.14.r422.g31453a9-1
| Git Clone URL: | https://aur.archlinux.org/x11vnc-git.git (read-only) |
|---|---|
| Package Base: | x11vnc-git |
| Description: | VNC server for real X displays |
| Upstream URL: | https://LibVNC.github.io |
| Licenses: | |
| Conflicts: | |
| Provides: | |
| Submitter: | bidulock |
| Maintainer: | bidulock |
| Last Packager: | bidulock |
| Votes: | 4 |
| Popularity: | 0.000000 |
| First Submitted: | 2014-09-22 04:28 |
| Last Updated: | 2016-06-13 10:55 |
Dependencies (14)
- avahi (avahi-git, avahi-nosystemd, avahi-gtk2)
- cairo (cairo-git, cairo-dfb, cairo-minimal, cairo-infinality, cairo-nomesa, cairo-infinality-ultimate, cairo-ubuntu)
- libvncserver-git
- libxcomposite
- libxcursor
- libxdamage
- libxinerama
- libxrandr (libxrandr-git)
- libxtst
- autoconf-archive (autoconf-archive-git) (make)
- java-environment (jdk6, jdk5, zulu-jdk, jdk9-openj9-bin, jdk7, tuxjdk, jdk8-openjdk-jetbrains, jdk8-openj9-bin, jdk7-openjdk-infinality, jdk9, java-8-openjdk-shenandoah, graal, jdk8-openjdk-infinality, intellij-jdk, jdk, jdk8, jdk-arm, jdk8-openjdk-shenandoah, graal-bin, java-gcj-compat, jdk-dcevm, jdk7-j9-bin, jdk7r1-j9-bin, jdk8-j9-bin, jdk-devel, jdk10-openjdk, jdk7-openjdk, jdk8-openjdk) (optional) – java-applet support
- net-tools (net-tools-mptcp, net-tools-debian-ifconfig, net-tools-git) (optional) – -auth guess
- tk (tk85) (optional) – GUI support
- xf86-video-dummy (optional) – Xdummy script
Required by (8)
- blink (requires x11vnc) (optional)
- epoptes-bzr (requires x11vnc)
- epoptes-client-bzr (requires x11vnc)
- gitso (requires x11vnc)
- let-me-do (requires x11vnc)
- pobvnc (requires x11vnc)
- pyvnc2swf (requires x11vnc)
- virtscreen (requires x11vnc)
Latest Comments
pmattern commented on 2015-10-26 22:01
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.