[BRLTTY] installation of systemd unit files

Anders Holmberg anders at pipkrokodil.se
Tue Apr 25 11:57:44 EDT 2017


Hi!
I didn’t even got the systemd thing to work.
I don’t know if you have to do something special but i followed the instructions on the website for brltty and got some no such file or directory messages when trying to systemctl start brltty.target.
I did run the make install in the systemd directory of brltty’s source directory.
Not sure if i have to first install brltty and then install the systemd thing.
If so it did not work.
/A
> 24 apr. 2017 kl. 23:17 skrev Mike Gorse <mgorse at alum.wpi.edu>:
> 
> Hi,
> 
> I am preparing an update to 5.5 for openSUSE and noticed that systemd unit files were being installed to /usr/lib64 on 64-bit systems, where our systemd unit files are under /usr/lib. I found this change:
> 
> From e89dd966fa6fcdb40b4de5f0385821604e21ef47 Mon Sep 17 00:00:00 2001
> From: Dave Mielke <dave at mielke.cc>
> Date: Thu, 30 Jun 2016 15:21:58 -0400
> Subject: [PATCH] The udev rules should be under /lib (not /etc). (dm)
> 
> This change also patched the systemd Makefile.in to use $(libdir), but the rationale isn't clear from the commit message, which only mentions udev. Is there a problem that is solved by this change?
> 
> For the moment, I've reverted that part of the commit in my openSUSE build, although I'm not sure if that is the thing to do upstream. Dbus has a configure option that allows the unit directory to be specified; maybe that is the thing to do.
> 
> Thanks,
> -Mike
> _______________________________________________
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY at brltty.com
> For general information, go to: http://brltty.com/mailman/listinfo/brltty



More information about the BRLTTY mailing list