On Mon, Feb 02, 2015 at 12:57:24PM +0100, Lennart Poettering wrote:
On Fri, 30.01.15 08:12, Peter Hutterer (peter.hutte...@who-t.net) wrote:
Hi,
I need some sort of way of assigning udev properties on the fly to a device,
but I'm short of ideas how to do this sensibly.
THis is
On Fri, 30.01.15 08:12, Peter Hutterer (peter.hutte...@who-t.net) wrote:
Hi,
I need some sort of way of assigning udev properties on the fly to a device,
but I'm short of ideas how to do this sensibly.
THis is explicitly not supported. Conceptually udev only supports new,
change and removed
On Fri, Jan 30, 2015 at 09:22:51AM +0100, Martin Pitt wrote:
Tomasz Torcz [2015-01-29 23:42 +0100]:
Have you seen umockdev? https://github.com/martinpitt/umockdev/
Right, with that you can run your tests as normal user, completely
isolated from the actual system, and you can set up/change
Peter Hutterer [2015-01-30 8:12 +1000]:
Because of uinput, the test suite runs as root. One solution would be to
drop a custom test rule, reload, create the uinput device, run the test,
rm the rule again. Not pretty though, I was hoping there was something
nicer.
I'm not aware of anything
Tomasz Torcz [2015-01-29 23:42 +0100]:
Have you seen umockdev? https://github.com/martinpitt/umockdev/
Right, with that you can run your tests as normal user, completely
isolated from the actual system, and you can set up/change devices,
attributes and properties at any time without
Hi,
I need some sort of way of assigning udev properties on the fly to a device,
but I'm short of ideas how to do this sensibly.
A bit more context:
The libinput test suite works by setting up uinput devices for each test
case, then hooking libinput contexts up to those devices. libinput itself
On Fri, Jan 30, 2015 at 08:12:54AM +1000, Peter Hutterer wrote:
Hi,
I need some sort of way of assigning udev properties on the fly to a device,
but I'm short of ideas how to do this sensibly.
Because of uinput, the test suite runs as root. One solution would be to
drop a custom test
