On Wed, 3 Mar 2021 at 18:25, Ed Greshko <ed.greshko(a)greshko.com> wrote:
On 04/03/2021 04:12, George N. White III wrote:
> Yes -- that is what how I understood the situation. The brltty devs
maintain Debian and
> RedHat packages with different post-install while creating groups with
systemd should
> work across distros (but the step to move the creation so systemd is
easily overlooked, and
> may not be noticed for a while since most installs will be upgrades
rather than fresh installs).
I don't known anything about Debian. But I did check the rpm's from F27
and the rpm's from
brltty.com.
The rpm's from
britty.com do not contain any scripts.
One of the advantages of systemd was supposed to be collecting some of the
hidden magic of package installers into more visible and less
distro-dependent
systemd files.
The rpm's from Fedora do contain scripts and the script which
creates the
group is within
the brlapi rpm and the group is created in the "normal" way. I don't know
what you mean
by "creating groups with systemd"
The PREIN script contains
getent group brlapi >/dev/null || groupadd -r brlapi >/dev/null
The Changelog at
britty.com for the 6.3 release says
the systemd component was changed to create the brlapi group if it
doesn't exist, so the same functionality as the script. Maybe the change
was a response to systems that failed to run the install script. What
creates the brltty group?
Additionally F34 will have brltty-6.3-1.fc34 which includes
brlapi-0.8.2-1.fc34 and that contains
the same PREIN script.
I live in a world that includes Ubuntu, macOS, and Windows. Organizations
I work
with use CentOS for large scale batch processing but make the users run
Windows, so
anything that makes it easier for developers to support multiple platforms
is of interest.
Thanks for checking the Fedora rpms. It looks like visually impaired
users will be
encountering lots of changes for Wayland and the sound system going forward.
--
George N. White III