#49: F13 X.org Test Week
-----------------------+----------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: task | Status: new
Priority: major | Milestone: Fedora 13
Component: Test Day | Version:
Resolution: | Keywords:
-----------------------+----------------------------------------------------
Comment (by adamwill):
just an update on this. Right now, I haven't added this to the schedule as
we'd like to figure out a date when we can be certain the hal -> udev
migration for input configuration has been done. Cut/paste dump from Peter
Hutterer:
---
There's one big chunk missing for 1.8 - the switch to udev instead of HAL
for input configuration. This requires transitioning the existing fdi
configurations into xorg.conf snippets and a (partial?) rewrite of fedora-
setup-keyboard. We don't have either of them yet, also because some
features (e.g. blacklisting devices) are still missing from upstream.
That however is something where a test day would be really useful, we
haven't gotten a lot of feedback (or testing) from that yet. I'm trying to
get all of the above done for F13, but...
---
there are four parts that need tackling:
- blacklisting devices requires an upstream change, I'm waiting for Dan's
answer on the current status.
- tagging system, waiting for Alberto Milane's answer on current status
- fedora-setup-keyboard: needs a good look. the current hal-callout
approach doesn't quite fit into udev afaict, so we need some different
approach.
- fdi migration: once we switch to udev, all existing custom fdi
migrations will break. not sure how many users have their custom ones, but
it'll be a fair chunk. we can either write some tool to do that or at
least document it on a wiki page. Given that they're xml files, it might
be possible to do something with xslt but I'm not sure i'm that
adventurous.
The last bit is the easiest one and could be done now, it's essentially
down to anything that currently has input.x11_option.Foobar needs to go
into an xorg.conf.d snippet as Option "foobar" <value>.
for the first two, we're essentially waiting on patches. fedora-setup-
keyboard could benefit from someone with an bit of understanding of
system-config-keyboard. I think the best approach here would be to run
f-s-k after s-c-k and dump an xorg.conf.d snippet into the directory that
matches on keyboards and sets all xkb options.
---
I had a look at f-s-k this arvo and rewrote it to work with the upcoming
udev support. The basic principle remains the same, all the HAL bits were
ripped out and instead it just drops 99-fedora-setup-keyboard.conf into
/etc/xorg.conf.d, which then looks like this on my box here:
Section "InputClass"
Identifier "fedora-setup-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "pc105+inet"
Option "XkbVariant" "us"
# Option "XkbModel" "(null)"
# Option "XkbOptions" "(null)"
EndSection
The new input attributes in the server means first match overrides, so
having 99-something.conf makes it a catchall for those that haven't been
set yet. a user can have a 10-my-keyboard.conf and that will take
precedence.
I've pushed it to the udev branch here:
git://people.freedesktop.org/~whot/fedora-setup-keyboard.git
what's next:
- actual testing beyond execution from the shell :)
- merging of the terminate_server option
- code review, I'm a bit cross-eyed today already
- integration - when can we actually call this?
- ...
- profit?
---
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/49#comment:4>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
