[Slackbuilds-users] jack-audio-connection-kit vs jack2
Ryan P.C. McQuen
ryan.q at linux.com
Thu May 28 22:16:19 UTC 2015
>But generally, that's all there is and I don't see a particular need to change that for whatever little benefit it would provide ...
I agree completely. Slackware is intended to be a system that treats
the user as if they are smart. Let's keep that tradition alive.
On 5/28/15, Heinz Wiesinger <pprkut at slackbuilds.org> wrote:
> On Thursday 28 May 2015 16:56:55 Klaatu wrote:
>> Fellow SBo maintainers:
>> I have noticed that one of my own scripts depends on JACK, and that I
>> myself had listed the dependency as "jack-audio-connection-kit".
>> Then I realised that this listing is not quite correct, because in fact
>> ANY package that depends upon "JACK" actually depends on EITHER JACK
>> version 1 or JACK version 2.
> Conflicting alternative packages are really nothing out of the ordinary.
> There's quite a few examples additionally to jack:
> - wxPython, wxGTK, wxX11
> - libav, ffmpeg
> - mysql, mariadb
> The general guidelines we try to follow is this:
> - All conflicting packages mention in the README what they conflict with
> jack-audio-connection-kit should mention it conflicts with jack2, and jack2
> should mention it conflicts with jack-audio-connection-kit)
> - One of the conflicting packages is picked and placed in REQUIRES,
> - Everything else is up to the user
> Obviously, mistakes/insonsistencies can happen, especially if alternatives
> introduced to the repo at a later stage. But generally, that's all there is
> and I don't see a particular need to change that for whatever little benefit
> would provide, but as usual, if the arguments are sound enough, every rule
> guideline is up for discussion.
More information about the SlackBuilds-users