Community Packages

Please read this before reporting a bug:

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!

FS#65073 - [espeak-ng] add `espeak`-compatibility.

Attached to Project: Community Packages
Opened by Oid Maps (dreieck) - Tuesday, 07 January 2020, 12:52 GMT
Last edited by Eli Schwartz (eschwartz) - Tuesday, 07 January 2020, 13:00 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



`espeak-ng` appears to be a drop-in replacement for `espeak`, if some symlinks are set. Consider doing that.

In the `PKGBUILD`s `package()`-function, adding the following lines at the end did make it compatible for me:

# Compatibilty-link for 'espeak':
cd "${pkgdir}/usr/lib"
for _ng_lib in*; do
ln -sv "${_ng_lib}" $(sed -E 's|\-ng\.|.|' <<< "${_ng_lib}"})
cd "${pkgdir}/usr/lib/pkgconfig"
ln -sv "espeak-ng.pc" "espeak.pc"
cd "${pkgdir}/usr/share"
ln -sv "espeak-ng-data" "espeak-data"

And then adding `provides=("espeak=${pkgver}")` did make the dependency available to `pacman`.
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Tuesday, 07 January 2020, 13:00 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#65072