[Slackbuilds-users] Jack policy

Dave Woodfall dave at slackbuilds.org
Mon Nov 25 06:01:54 UTC 2019

On 2019-11-24 14:38,
Franzen <slackbuilds at schoepfer.info> put forth the proposition:
> Hi,
> as there is no 'or/||' possible in the REQUIRES tag, installing package "a"
> with REQUIRES=jack-audio-connection-kit
> and then installing package "b" with REQUIRES=jack2 will end with a broken
> jack, as jack-audio-connection-kit and jack2
> are conflicting packages. Details at https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2
> Grepping throus SBo git shows
> slackbuilds> find . -type f -iname '*info' -exec grep -H REQUIRES '{}' + |
> grep jack-audio-connection-kit  | wc -l
> 73
> slackbuilds> find . -type f -iname '*info' -exec grep -H REQUIRES '{}' + |
> grep jack2  | wc -l
> 6
> If i change my builds to jack-audio-connection-kit, then there will only be
> two builds left with dep on jack2, namely
> MuseScore and lives.
> If their maintainers have no problem with jack-audio-connection-kit, maybe
> jack-audio-connection-kit could
> be handled as default jack on SBo?

Personally, I find changing things to jack-audio-connection-kit from jack2 is
a regression, and I'd recommend going the other way.  I don't know the reasons
that people stick to the now very old version.

I've been running jack2 for several years and had no problems with it, or had
to downgrade to the older jack.  It's also what all the apps on Studioware
use, and there haven't been any problems reported about it.

This is just my 2 pennies though, speaking as an everyday jack user.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20191125/7f166bd2/attachment-0001.asc>

More information about the SlackBuilds-users mailing list