Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#71530 - [brltty] split out libbrlapi?

Attached to Project: Arch Linux
Opened by Neven Sajko (Neven) - Saturday, 17 July 2021, 11:06 GMT
Last edited by David Runge (dvzrv) - Thursday, 14 October 2021, 16:34 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

It would be great if libbrlapi could be split from the brltty package, like in Debian.

This would enable qemu to lose the dependency on brltty, and many users who only had brltty installed because qemu depends on it could be free of brltty and, especially, brltty's recursive dependencies. Libbrlapi would have comparatively minimal dependencies as a package.

It's clear that most people who install qemu don't have any need for brltty. See the pkgstats package prevalence for brltty and the only two packages that depend on it:

brltty 40.95
qemu 38.20
orca 15.36

Some specific packages that would no longer be required at least on my Arch system if libbrlapi was split from brltty, with the qemu package switching to depend on libbrlapi; are:
* brltty
* the deprecated bluez-libs
* libspeechd
* polkit
* js78

In the case of polkit, it's not just about having an unnecessary package installed, because polkit is impossible to disable once installed.

Additional info:
* package versions: brltty 6.3-3, qemu 6.0.0-3
This task depends upon

Closed by  David Runge (dvzrv)
Thursday, 14 October 2021, 16:34 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed via making brltty an optional dependency for qemu: https://bugs.archlinux.org/task/72312
Comment by Alexander Epaneshnikov (alex19EP) - Monday, 11 October 2021, 14:55 GMT
I think  FS#72312  will fix this.

Loading...