summaryrefslogtreecommitdiff
path: root/x11/xkbcomp
AgeCommit message (Collapse)AuthorFilesLines
2009-11-09Update to xkbcomp-1.1.1. Changes:tnn2-6/+6
xkbcomp: Remove output file if closing fails.
2009-07-18Update to 1.1.0:wiz2-6/+6
xkbcomp wanted a release. This version does not have a lot of new features but enough code was modified to justify the 1.1.0 bump. The most interesting feature is the ability to configure the xkb data dir at configure time rather than being forced to the hardcoded default. Other changes include a few bug fixes, cleanups, comments and a run of 'indent' over the repository. The latter may require distribution patches to be adjusted. Cheers, Peter Alan Coopersmith (5): Check for strdup & strcasecmp before assuming we need to provide our own Remove X_NOT_POSIX #ifdefs Remove #if 0'd typedef that appears nowhere else. sprintf -> snprintf conversions Use temporary buffer for generating Uxxx names to avoid overflow Dan Nicholson (1): Allow the default XKB config root to be set from configure Matthieu Herrb (1): Minimal man page addition for new -i option. Paulo Cesar Pereira de Andrade (2): Correct make distcheck and most gcc and sparse warnings. Correct a remaining of a wrong change to make some DEBUG_VAR's static. Peter Hutterer (13): Remove RCS tags. Add a few explanatory comments. Indent fixes. If we're not using XkbDesc, don't require it as a parameter. Add some explanatory comments Silence valgrind warnings. Remove useless longestPath variable. More comments. Don't pass useless handlers around in HandleIncludeKeycodes. Remove unused merge parameter from HandleKeyNameVar. Don't overwrite previously assigned type indices with useless ones. Check for NULL strings before calling strdup. Bump to 1.1.0.
2008-05-24Switch master site to MASTER_SITE_XORG.tnn1-2/+2
2008-05-09Update to xkbcomp 1.0.5.bjs2-6/+6
commit 1aecdffaa0db7bbf85bc0aae9043e9437b25c30d Author: Daniel Stone <daniel@fooishbar.org> Date: Thu Apr 17 00:52:29 2008 +0300 Don't scan paths which make NO SENSE WHATSOEVER TO SCAN Hey, I wonder if we have XKB files in our directory! I wonder if we haven't bothered with a structure, and let's try to open a file called 'misc' in someone's home directory! What a surprise, it's not a valid XKB file! Let's fail miserably! SURPRISINGLY, THIS IS NOT USEFUL BEHAVIOUR. commit a3a05fd489a9a35942a4419c537634e796dbebd1 Author: Daniel Stone <daniel@fooishbar.org> Date: Thu Apr 17 00:50:07 2008 +0300 xkbcomp: Take a device ID argument Allows the user to set maps (or whatever) on arbitrary devices.
2008-04-16Update to 1.0.4:wiz3-24/+6
Adam Jackson (2): Bug #7645: Fix a conditional that always evaluates to FALSE. xkbcomp 1.0.4 Alan Coopersmith (1): Bug 14185: MAINTAINERCLEANFILES multiply defined in Makefile.am Daniel Drake (1): Bug #11025: xkbcomp COPYING file James Cloos (3): Rename .cvsignore to .gitignore Add *~ to .gitignore to skip patch/emacs droppings Replace static ChangeLog with dist-hook to generate from git log Matthieu Herrb (2): Also mark xkbparse.h as a generated file. Revert "Also mark xkbparse.h as a generated file." Tilman Sauerbeck (3): Fixed an invalid memory access. Fixed a bunch of const correctness bugs. Ignore *.o and ylwrap.
2007-05-07Fix man page suffix on Linux. List from Alexander Nason on pkgsrc-users.joerg1-1/+3
2007-02-26update to 1.0.3drochner3-6/+24
changes: accept negative numbers in geometry co-ordinates avoid use of uninitialised variable
2006-11-07Import xkbcomp-1.0.2:joerg4-0/+32
The xkbcomp tool converts descriptions of an XKB keymap into other formats, most importantly the compiled keymaps used by XKB-capable X servers.