<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>hi<br>
</p>
I'm on kernel version 4.7, but I also have the 4.4 lts installed. I
should probably try that one. I'll add the files into our
packages-extra repo.<br>
Thanks<br>
Kendell Clark<br>
<br>
<div class="moz-cite-prefix">On 08/30/2016 06:55 PM, Bernhard
Landauer wrote:<br>
</div>
<blockquote
cite="mid:4f1fedd9-cc25-d0d7-3aae-5eec75745a37@manjaro.org"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=windows-1252">
<p>Hi Kendell.<br>
Yes, it would be good to add the files in our repo so we have
them ready whenever we need them in the future :)<br>
I can try building the 32bit here and see if I have more
success...<br>
What kernel version are you running?<br>
kind regards<br>
Bernhard<br>
</p>
<br>
<div class="moz-cite-prefix">On 31/08/16 01:28, kendell clark
wrote:<br>
</div>
<blockquote
cite="mid:ee569b69-c09e-494f-64a3-818584eed9f6@gmail.com"
type="cite">
<p>hi<br>
</p>
Thanks a lot bernhard for that tip. I've updated the pkgbuild
and have uploaded the 64 bit package. Should I also add the
pkgbuild and the supporting service and install files to the
packages-extra repo, or do you want to rely on the arch package?
The only thing ours does differently is to add that
"api-parameters auth=polkit" config option to /etc/brltty.conf,
and it's already there we're just removing the comment. It also
copies the polkit rule file from
"authorization/org.brltty.policy" to
/usr/share/polkit-1/rules.d, and those two lines can easily be
contributed upstream, if the arch people will take them. They
can be a little ... mmm ... iffy on accepting help. At least
that's what I've noticed. I've been trying to upload a 32 bit
package but I keep running into that "main: unable to allocate
memory" error in buildpkg, even after changing the make line to
"make -j1". I'm stumped on that one.<br>
Thanks<br>
Kendell Clark<br>
<br>
<div class="moz-cite-prefix">On 08/30/2016 02:21 AM, Bernhard
Landauer wrote:<br>
</div>
<blockquote
cite="mid:67697781-f040-3885-b16b-37c70a94418a@manjaro.org"
type="cite">
<p>Hi Kendell.</p>
<p>If you like I can edit your PKGBUILD tonight. Atm I do't
have the computer on me ...<br>
But you can just do it by adding this sed line at the end of
package() function:<br>
</p>
<p>sed -i '/Auth=polkit/s/^#//' $pkgdir/etc/brltty.conf</p>
<p>kind regards<br>
Bernhard<br>
<br>
</p>
<div class="moz-cite-prefix">On 30/08/16 07:27, kendell clark
wrote:<br>
</div>
<blockquote
cite="mid:e7ecd88d-e5ea-564f-a9f6-289e049fc2ed@gmail.com"
type="cite">hi all <br>
<br>
Since brltty 5.4 is out, I decided to look at the changes.
One very important change is that brltty can now use policy
kit to grant access to braille devices instead of relying on
the permissions of the /etc/brlapi.key file being set
properly. This makes it much much easier for me to make
braille work out of the box on sonar. However, I'm not sure
how to modify the pkgbuild how it needs to. All that's
needed is for a script to remove the comment sign in front
of <br>
<br>
api-parameters Auth=polkit # authenticate via Polkit
<br>
<br>
in the config file, which is in /etc/brltty.conf. The line
would need to be after the line that copies that file into
/etc because before it's in the "Documents" folder. I'm
attaching the pkgbuild, already updated to use 5.4, with the
correct md5-sums for the modified service file. I've tarred
them all up into an archive since the pkgbuild, service file
and the install file all need to be in the same folder
together. Would someone mind maybe looking into what might
be needed to remove that comment so that braille works out
of the box? I'm just about to take a nice long nap. If no
one's looked at it by the time I wake up I'll try to take a
look myself. Don't worry I'm not rushing or ... yawn ...
anything, man I'm tired. This is important but by no means
critical. <br>
<br>
Thanks <br>
<br>
Kendell Clark <br>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
manjaro-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.manjaro.org/mailman/listinfo/manjaro-dev">http://lists.manjaro.org/mailman/listinfo/manjaro-dev</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
manjaro-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.manjaro.org/mailman/listinfo/manjaro-dev">http://lists.manjaro.org/mailman/listinfo/manjaro-dev</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
manjaro-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.manjaro.org/mailman/listinfo/manjaro-dev">http://lists.manjaro.org/mailman/listinfo/manjaro-dev</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
manjaro-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a>
<a class="moz-txt-link-freetext" href="http://lists.manjaro.org/mailman/listinfo/manjaro-dev">http://lists.manjaro.org/mailman/listinfo/manjaro-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>