Package Details: xkeyboard-config-chromebook 2.20-1

Git Clone URL: https://aur.archlinux.org/xkeyboard-config-chromebook.git (read-only)
Package Base: xkeyboard-config-chromebook
Description: X keyboard configuration files
Upstream URL: https://www.freedesktop.org/wiki/Software/XKeyboardConfig
Licenses: custom
Conflicts: xkbdata,, xkeyboard-config
Provides: xkbdata,, xkeyboard-config
Replaces: xkbdata
Submitter: dhead666
Maintainer: evana
Last Packager: evana
Votes: 7
Popularity: 0.102059
First Submitted: 2014-09-17 21:26
Last Updated: 2017-02-20 18:55

Pinned Comments

evana commented on 2017-02-20 18:57

I have adopted the package and brought it inline with the current official repository state. I'm considering switching over to the keyboard mappings from GalliumOS, but would like your opinions on the matter first. Gallium's keybindings are detailed here: https://wiki.galliumos.org/Media_keys_and_default_keybindings, and the patch is available here: https://github.com/GalliumOS/xkeyboard-config/blob/master/debian/patches/chromebook.patch

Latest Comments

nariox commented on 2017-06-12 20:00

This is unrelated to xkeyboard (in terms of why it didn't work), you need to add the gpg keys to your keyring.

You can check this thread for more info:
https://bbs.archlinux.org/viewtopic.php?id=191629

rabarrett commented on 2017-06-10 04:10

https://pastebin.com/Z4qzZwsG

nariox commented on 2017-06-09 15:53

Hi @rabarrett,
I've just rebuilt it fine in my C720. Were you able to build it earlier? Make sure you have base-devel installed. Some dependency might be missing. Could you post an more detailed log of the build failure?

rabarrett commented on 2017-06-07 22:26

When I try to update, I now get:
ERROR: Makepkg was unable to build xkeyboard-config-chromebook

IS this related to switching over to GalliumOS? Is the switch taking place? It seems a positive move to me, but there are no comments since the February 20 discussion of it.

nariox commented on 2017-02-20 21:57

Oh, I see, so in addition to the current keyboard layouts it offers additional layouts (Media/Function by default, Right Alt/Super as Overlay), correct?

In that case, I don't see why not to switch, since all original functionality seems to be kept and new functionality is added. Besides, maintainability is another big upside.

evana commented on 2017-02-20 21:46

@nariox

Gallium's config is more fully featured than what this package currently provides, and it provides multiple configurations to suit individual preferences. It would definitely be helpful for maintainability since the gallium devs already put a lot of time into chromebook compatibility.

nariox commented on 2017-02-20 19:47

Hi evana,
I took at look at the GalliumOS patch, but couldn't figure out what is the difference (in terms of functionality) between this is the current implementation? If they are the same (or at least similar enough), I feel it'd make sense to make the switch (I'm imagining one advantage would be maintainability).

evana commented on 2017-02-20 18:57

I have adopted the package and brought it inline with the current official repository state. I'm considering switching over to the keyboard mappings from GalliumOS, but would like your opinions on the matter first. Gallium's keybindings are detailed here: https://wiki.galliumos.org/Media_keys_and_default_keybindings, and the patch is available here: https://github.com/GalliumOS/xkeyboard-config/blob/master/debian/patches/chromebook.patch

dhead666 commented on 2015-09-18 03:44

oh darn, I'll give this a look after 3.18 release.

nariox commented on 2015-09-16 01:57

@dhead: oh noes, seems like GNOME devs removed another functionality, accel maps have been disabled since 3.15.4 ):
https://github.com/GNOME/nautilus/blob/master/NEWS

All comments