You are not logged in.
Pages: 1
hi forum,
a little issue regarding the denemo package.
I wouldn't call it a bug since
1. it should be fixed upstream, and
2. it only occurs when AUR is involved.
denemo includes libsmf, which is shared by a few applications
(I know of denemo, mididings and jack-smf-utils).
Maintaining jack-smf-utils in AUR I 'was stumbled' across this
issue. jack-smf-utils contains libsmf, just like denemo, leading
to file conflicts. jack-smf-utils is now fixed to exclude and
depend on libsmf. mididings did so before.
I have sent patches upstream for denemo and jack-smf-utils.
For testing purposes, I uploaded a version of denemo to
AUR that is patched to exclude and depend on libsmf [1].
[1] http://aur.archlinux.org/packages.php?ID=40705
To me it seems reasonable to include libsmf in community
and let denemo depend on it. The number of apps depending
on libsmf will most likely not decrease in the future. :)
libsmf
http://aur.archlinux.org/packages.php?ID=39394
jack-smf-utils
http://aur.archlinux.org/packages.php?ID=33094
Offline
Pages: 1