Stefan Dirsch
8cf76eaac9
This release is mostly all about keysyms. Some additions to Vietnamese and Hangul but the big set of commits here is catching up with several years of Linux kernel releases. The kernel's evdev interface has semantic keycodes (e.g. KEY_ESC is what you'd expect). Beyond the normal range expected to change with different layouts there are many keycodes that should only ever do one thing. For example, KEY_ONSCREEN_KEYBOARD should display the OSK regardless of layout). In the past, we've added these keysyms on a as-requested basis. We now have a reserved subrange in the already reserved range for XF86Foo keysyms. Within that range, keysyms map directly to their evdev counterparts, making future updates easier. The above example KEY_ONSCREEN_KEYBOARD now has a XF86OnScreenKeyboard keysym. The header file follows a strict convention to make this range machine-readable, xkeyboard-config can make use of this to make those keysyms available by default. Note that almost all keys are outside the X keycode range so very little will change under X. Note that most keys exist on selected devices only so the practial use is quite limited. But those keysyms are available through normal XKB configuration so users can re-map existing keys where needed. Aside from those, a bit of misc cleanup work. Many thanks to all contributors. OBS-URL: https://build.opensuse.org/package/show/X11:XOrg/xorgproto?expand=0&rev=11
86 lines
3.8 KiB
Plaintext
86 lines
3.8 KiB
Plaintext
-------------------------------------------------------------------
|
|
Thu Feb 25 10:39:54 UTC 2021 - Stefan Dirsch <sndirsch@suse.com>
|
|
|
|
- xorgproto 2021.2
|
|
This release is mostly all about keysyms. Some additions to Vietnamese and
|
|
Hangul but the big set of commits here is catching up with several years of
|
|
Linux kernel releases.
|
|
|
|
The kernel's evdev interface has semantic keycodes (e.g. KEY_ESC is what
|
|
you'd expect). Beyond the normal range expected to change with different
|
|
layouts there are many keycodes that should only ever do one thing.
|
|
For example, KEY_ONSCREEN_KEYBOARD should display the OSK regardless of
|
|
layout). In the past, we've added these keysyms on a as-requested basis.
|
|
|
|
We now have a reserved subrange in the already reserved range for XF86Foo
|
|
keysyms. Within that range, keysyms map directly to their evdev
|
|
counterparts, making future updates easier. The above example
|
|
KEY_ONSCREEN_KEYBOARD now has a XF86OnScreenKeyboard keysym.
|
|
The header file follows a strict convention to make this range
|
|
machine-readable, xkeyboard-config can make use of this to
|
|
make those keysyms available by default. Note that almost all keys are
|
|
outside the X keycode range so very little will change under X.
|
|
|
|
Note that most keys exist on selected devices only so the practial use is
|
|
quite limited. But those keysyms are available through normal XKB
|
|
configuration so users can re-map existing keys where needed.
|
|
|
|
Aside from those, a bit of misc cleanup work. Many thanks to all
|
|
contributors.
|
|
|
|
-------------------------------------------------------------------
|
|
Tue Apr 14 21:22:36 UTC 2020 - Stefan Dirsch <sndirsch@suse.com>
|
|
|
|
- xorgproto 2020.1
|
|
* This release adds a new keysym, a state-change event to the
|
|
DPMS extension, synchronizes more of the meson and autotools
|
|
build sytems, and converts some quasi-text documentation to
|
|
Markdown.
|
|
|
|
-------------------------------------------------------------------
|
|
Fri Oct 18 10:05:56 UTC 2019 - Stefan Dirsch <sndirsch@suse.com>
|
|
|
|
- xorgproto 2019.2
|
|
* This release moves more header files to the legacy set. Note
|
|
that this means libX11 older than 1.6.9 and libXvMC older
|
|
than 1.0.12 will not build without some legacy headers installed.
|
|
|
|
-------------------------------------------------------------------
|
|
Mon Jun 24 14:28:53 UTC 2019 - Stefan Dirsch <sndirsch@suse.com>
|
|
|
|
- use --enable-legacy configure option on existing products in order
|
|
not to break package builds, which still requires any of these
|
|
extensions:
|
|
* trapproto
|
|
* xf86miscproto
|
|
* xproxymngproto
|
|
deleterequests for the affected packaages have been done for factory/TW
|
|
|
|
-------------------------------------------------------------------
|
|
Fri Jun 21 10:08:56 UTC 2019 - Stefan Dirsch <sndirsch@suse.com>
|
|
|
|
- xorgproto 2019.1
|
|
* This release boasts a bunch of cleanup work and a few new
|
|
keysyms. No functional changes to any of the protocols.
|
|
|
|
-------------------------------------------------------------------
|
|
Wed Jun 27 23:07:34 UTC 2018 - tobias.johannes.klausmann@mni.thm.de
|
|
|
|
- Obsolete protocol packages by their corresponding old package names, not by
|
|
their pkconfig(...) provides. Additionally move the obsoletes to the -devel
|
|
package to take effect.
|
|
|
|
-------------------------------------------------------------------
|
|
Wed Feb 28 20:45:12 UTC 2018 - tobias.johannes.klausmann@mni.thm.de
|
|
|
|
- Create package xorgproto with initial version 2018.4:
|
|
This package contains all previously split up xorg protocol headers in one
|
|
package (again!). Additionally this package contains two new protocol
|
|
versions required by the upcoming XServer 1.20:
|
|
+ dri3proto version 1.2
|
|
+ randrproto version 1.6
|
|
- Obsolete the old *prot packages by using the actual protocol version to keep
|
|
this package compatible with the old versioning scheme.
|
|
- "Prefer: xorgproto-devel" in the project config is required to prefer it for
|
|
now
|