Package Details: xdotool-git 3.20160805.1.r24.g6523b5f-1

Git Clone URL: https://aur.archlinux.org/xdotool-git.git (read-only, click to copy)
Package Base: xdotool-git
Description: Command-line X11 automation tool (git version)
Upstream URL: https://www.semicomplete.com/projects/xdotool/
Licenses: BSD
Conflicts: xdotool, xdotool-svn
Provides: xdotool
Replaces: xdotool-svn
Submitter: lowfatcomputing
Maintainer: dbermond
Last Packager: dbermond
Votes: 17
Popularity: 0.000000
First Submitted: 2011-02-27 00:44 (UTC)
Last Updated: 2019-06-02 14:31 (UTC)

Required by (236)

Sources (1)

Latest Comments

dbermond commented on 2025-08-12 14:57 (UTC) (edited on 2025-08-12 14:58 (UTC) by dbermond)

@jpka AUR helpers are not supported, use makepkg. That being said, I have just checked, and the package is building perfectly fine in an Arch Linux system with makepkg or devtools.

jpka commented on 2025-08-12 09:05 (UTC)

Hello.

Trying to yay -S xdotool-git, it exits with /bin/sh: line 1: pod2man: command not found. Using yay -S pod2man (there is no pod2man-git), it says No AUR package found for perl=5.40.2. Trying yay -S perl it says perl-5.42.0-1 is up to date. There is no yay -Ss perl-5.40.2. Is it pod2man error?

Thanks.

saxa commented on 2025-07-11 11:21 (UTC)

@dbermond yes you're right that was supposed to go to kdotool-git. Sorry about the wrong report.

dbermond commented on 2025-07-10 16:22 (UTC)

@saxa I have just checked, and the package is building perfectly fine. I have the feeling that you are reporting to the wrong package, as xdotool does not use rust/cargo.

saxa commented on 2025-07-10 15:51 (UTC) (edited on 2025-07-11 11:14 (UTC) by saxa)

Would like to install this as I need it for some scripting tasks, however I'm getting a build error: failed to run custom build command for cargo-husky v1.5.0. Tried cleanbuild and --rebuild.

Sorry this was supposed to go to the kdotool-git package.

dbermond commented on 2017-10-01 14:08 (UTC)

I have adopted this package. Among other changes, pkgver is now fixed. Enjoy using xdotool-git.

eigengrau commented on 2017-02-16 09:02 (UTC)

Hello lowfatcomputing. Your pkgver() is currently broken and does not return a release number, making pacman think the package is being downgraded on upgrades. Also, the way you build the package still makes the binary vulnerable to code-injections. This is a serious problem and is easily fixed by changing a few characters. Please see my comment from 2015.

eigengrau commented on 2015-09-12 19:50 (UTC)

Please use «make PREFIX=/usr» instead of «make PREFIX="$pkgdir"/usr». The actual install location can be supplied to make with «make DESTDIR="$pkgdir" install» during the installation phase. Otherwise, references to the build directory can wind up in the built binary. In this case, the current PKGBUILD will cause a location in /tmp to be added to the executable’s RPATH, which enables other users to inject code into the xdotool binary, which could then be executed by unsuspecting victims.

neven commented on 2015-03-18 13:38 (UTC)

You need depends=(libxkbcommon libxinerama libxtst) and conflicts=(xdotool) .