FS#54987 - [ejabberd] Symlink /usr/lib/ejabberd to the current /usr/lib/ejabberd-$pkgver
Attached to Project:
Community Packages
Opened by Martin Schulze (schulmar) - Monday, 31 July 2017, 11:06 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 01 August 2017, 09:13 GMT
Opened by Martin Schulze (schulmar) - Monday, 31 July 2017, 11:06 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 01 August 2017, 09:13 GMT
|
Details
With every update to ejabberd the path to the captcha.sh
(/usr/lib/ejabberd-$pkgversion/priv/bin/captcha.sh) has to
be changed in the configuration file, where it defaults to
/usr/lib/ejabberd/priv/bin/captcha.sh. This is tedious and
error prone and I think unnecessary:
For some time I have manually maintained a link /usr/lib/ejabberd -> ejabberd-$pkgversion but this is error prone as well. Since version 17.07-1 (https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/ejabberd&id=7643c0ed8b1a5f4ad7f3a1915d9cbab0b7e2114b) this is not possible anymore, as there is now /usr/lib/ejabberd/priv/bin/epam. I am not sure why this change was introduced but epam formerly lived in /usr/lib/ejabberd-$pkgversion/priv/bin/ so it should be possible to access it via /usr/lib/ejabberd/priv/bin/epam with the help of said symlink. Are there any reasons not to provide this symlink in the package itself? |
This task depends upon
FS#53607May I ask why we even have the version in the lib path? It seems that upstream does not intend for that.
There's a link the the Reporting Bug Guidelines at the top of the bugtracker interface.
The Severity section discusses the differences in severity; for optional functionality that requires configuration updates on package upgrades, this is not so severe. Severity is not a matter of how quick the *workaround/fix* is, but of how much impact the *problem* has. :)
Quick workarounds/fixes are great -- it just means bugs can be resolved faster.