[BRLTTY] Packaging questions

[Peter Vágner]

Hello,


2017-10-25 19:38 GMT+02:00 Didier Spaier <didier at slint.fr>:

>
> I don't see links associated to the number under brackets like [1].
> Maybe you forgot to append them?
>
> Oh yes damn. It took me ages to write all this down, then I had issues
posting to the list because I was not paying attention to the mailman
introductory messages when joining the list.
Here are the links I wanted to include in the original message.
[1]:
http://brltty.mielke.narkive.com/nWBtM3ui/problem-with-brltty-and-polkit
[2]: https://mail.gnome.org/archives/orca-list/2017-October/msg00313.html
[3]:
https://github.com/xenserver/xen-4.5/commit/e6c3d371d475a10d2ebe9351472a2ec261023d72
[4]: https://mail.gnome.org/archives/orca-list/2017-October/msg00310.html


> Well, I don't know the Arch build system but generally speaking it's
> safe no to include options unless you want to exclude some stuff from the
> package, and configure will just build according to the installed deps
> at that time in the host system. Let me give two examples.
>
Yes this is a principle I would like to adopt however I don't necessarily
like to create a minimal package as I can see  Dave, Samuel and others have
put really a huge effort to create the awesome software with wel written
documentation. I am using arch linux for a few years now and I can see
brltty is treated like ordinary user managed service. Also I see some
packages are excluded such as audio support, x11 support and more. I would
just like to try to understand if that's usefull to users and package it
properly. Arch has an ability to specify even optional dependencies. It's
kind of do it your self distribution but then all common software features
should be possible. If there are users who might like to have audio and
speech support in brltty I would like them to have it. Perhaps I will have
difficulties to adding this to the official arch repositories but still I
believe ignoring it just wastes Brltty developer's effort at the first
place.


> 2) In the installer the package is stripped down this way:
> ./configure \
>   --prefix=/usr \
>   --bindir=/bin \
>   --sbindir=/sbin \
>   --libdir=/lib${LIBDIRSUFFIX} \
>   --infodir=/usr/info \
>   --mandir=/usr/man \
>   --sysconfdir=/etc \
>   --localstatedir=/var \
>   --build=$ARCH-slint-linux \
>   --disable-contracted-braille \
>
Are you sure you would like to disable contracted braille? I think people
reading and writing english, german, french braille and other braille codes
where there is contracting support tend to prefer contracted braille over
uncontracted braille.

>   --disable-speech-support \
>   --disable-icu \
>
This is related to localization am I right? I guess you are targetting at
least two localizations english and french, perhaps you also need to
reconsider this.

>   --disable-x \
>   --disable-gpm \
>
In arch this is explicitly enabled. It has something to do with the mouse
as I have understood. Perhaps it's usefull for copying and pasting on text
console or perhaps scrolling. I am not sure however since it's enabled in
arch and in debian I guess it's usefull.

>   --disable-api \
>
What API does this disable? I guess not brlapi as I have seen your earlier
discussion with Dave and Samuel where you have understood you do need to
include brlapi for allowing orca communicating to brltty.

>   --disable-ocaml-bindings \
>   --disable-java-bindings \
>   --disable-lisp-bindings \
>
You might need this for speechd-el braille support

>   --disable-python-bindings \
>
You need this for orca...
Or err.. I see you are building brlapi seperatelly am I correct?

>   --disable-tcl-bindings \
>   --disable-polkit \
>   --with-pcm-package=no \
>   --with-midi-package=no \
>   --with-fm-package=no \
>   --with-curses=ncurses \
>   --with-bluetooth-package=no
>
> As you see we don't include the bindings, all stuff needed for speech
> support (as we use speakup instead), polkit (we are root during
> installation), etc.
>
Polkit is not for installation as I am understanding it. Polkit is for
authorizing brlapi clients such as orca using python-brlapi or speechd-el
using brlapi lisp bindings to talk to brltty built-in brlapi server. This
is not the only supported auth method and for all slint desktops except of
mate and kde this is not needed as I think these lightweight desktop
environments don't use polkit either. I will hopefully understand this
better once my question related to brlapi client config is cleared up.

>
>
> You can use the tty device like in this example:
> brltty -b tt -d /dev/tty12 and you will get the output on /dev/tty12
> Thanks again Samuel for the tip!
>
> Yeah, awesome I will play with this tonight.

>
> PS I will upload a Slint64-14.2.1RC2 ISO real soon now, then wait a few
> days for comments. Peter, I will be especially eager to hear from you ;)
>
> Yes, I will check it out as I have never experiences attempt at
accessibility enabled kde. And perhaps I'll be able to check the others in
the process.

Thanks and Greetings

Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://brltty.com/pipermail/brltty/attachments/20171025/3e0a1ba6/attachment.html>