Denis Barbier <barbier@linuxfr.org> writes: > Hi, > > I have built a Debian package of brltty 3.7.2, the changelog entry is at > the bottom. Thanks for working on this, but see below. > I have no braille device to test this package, but it seems to work, > the new X-Window module prints something. This module pulls in some > packages from X11. I would say that this is acceptable because > developments for many assistive technologies are now based on X, but > maybe some people would prefer a stripped down package. Yes, I definitely prefer splitting out the heavy-wheighted modules like xw and the atspi screen driver into a separate package. brltty should be installable on a machine, without pulling in all sorts of things. I've done that change in my local 3.7.2 package already, + a brltty-flite package. I.e., brltty-x11 contain the xw and the atspi screen driver, and brltty-flite the fl driver. > Packages are available at > http://people.debian.org/~barbier/tmp/brltty/ > and built for sid. > Mario, will you have some time to have a look and incorporate the > changes you like in your version? I am already looking. > Otherwise, may I upload this into unstable? Thanks. Please dont, see below. > brltty (3.7.2-0.1) unstable; urgency=low > > * Non-maintainer upload. > * New upstream release. (Closes: Bug#343122 which is a request for this update) > * Killing brltty sometimes take a long time, thus replace the 5s delay in > /etc/init.d/brltty by start-stop-daemon --retry 5. (Closes: Bug#313262) > Thanks Samuel Thibault for the report and a patch. > * Fix a typo in brltty.postrm so that /etc/brlapi.key is removed when > purging. (Closes: Bug#327238) > * Modify debconf scripts to avoid the "debconf is not a registry" trap. > brltty.config now sets debconf values with those found in /etc/brltty.conf. > The mapping between drivers code and name is put in debian/map.* files, and > templates and config scripts take their values from these files. I gave this brltty.config a read, and can not see any multiple driver/device handling. I guess you did not know, but one of the really cool features about 3.7 is that we now have autodetection capabilities. This means: braille-driver can be a comma-separated list, listing all drivers to try, or "auto", which means try all possible given the device(s) specified. braille-device can also be a comma-separated list, specifying all devices (busses) to search for bralle displays. Some examples: 1. I have a braille display with either serial, usb or bluettoth connection possibility, which is handled by the "ht" braille driver. To get all three working without having to reconfigure/start brltty, I specify: braille-driver ht braille-device serial:/dev/ttyS0,usb:,bluetooth:xx:xx:xx:xx:xx:xx (the xx:xx... is the hex bluettoth address of my display). This makes brltty try to initalize the ht driver with each of the specified devices (i.e., check ttyS0, look on the usb bus, try to connect via bluettoth). So I can change from say, USB to bluettoth on the fly, and brltty simply re-finds the device. With the old config method, I would have had to change the config before switching, which is extremely unreliable. 2. For added measure, I could write my config such that braille-driver is auto, so all drivers capable of autodetecting on the serial port, all usb capable drivers and all bluetooth caable drivers will be tried. This would make all USB displays supported by brltty work on my workstation, without any config changes, plug any play + my personal display via bluetooth. 3. We therefore should aim for a default config of /etc/brltty.conf for new installations which actually does: braille-driver auto braille-device usb: since USB autodetection is based on USB product/vendor IDs, and therefore very reliable. This would make brltty work for USB display users (which are the standard for new products) out of the box, without any configuration required by the user. Now, as you can see, this gets very complicated if implemented with debconf (at least IMO). I therefore planned to drop debconf support, and require the user to configure /etc/brltty.conf manually. Comments? I gather you are lots better with debconf coding then I am, do you think the above scheme is doable with scripting? If so, we'd need t do this, or drop debconf support. Addtionally, there is a bug in 3.7.2 which is fixed upstream and affects some USB displays. This patch at least should be applied, I've done this already with my local package. Additionally, I think we need to rename libbrlapi, to libbrlapi1 (and the -dev package accordingly) to avoid unnecessary breakage upon upload since the ABI/API changed. > * Replace perl code by sed in brltty.postinst. > * New debconf translations: > - Swedish, by Daniel Nylander (Closes: Bug#341029). > - Vietnamese, by Clytie Siddall (Closes: Bug#313182). > * Update German debconf translations, by Jens Seidel (Closes: Bug#314146). > > -- Denis Barbier <barbier@debian.org> Thu, 16 Feb 2006 21:21:26 +0100 > -- CYa, Mario
Attachment:
pgpOlw2Qj7Hdz.pgp
Description: PGP signature