[Slackbuilds-users] Which jack?

[Didier Spaier]

PS: this would help also for case like portaudio or speech-dispatcher
for instance, as they need the support of at least an audio backend, but
can safely be built with several ones.
So for espeak.info the REQUIRES line could include:
alsa|jack1|jack2|oss
And for speech-dispatcher.info:
pulse|libao|alsa|oss|nas
Maybe in these cases this is an overkill, as oss, alsa and pulse are
included in a full Slackware installation (at least either alsa or
pulse in Slackware-current) and thus maybe should not be mentioned in
the REQUIRES line, but you get the idea.

These examples also illustrate that the vertical line should mean "or",
not "xor".

Didier


On 24/12/2018 19:55, Klaatu wrote:
> I quite like this idea.
> 
> On 24 December 2018 10:41:47 PM NZDT, Didier Spaier <didier at slint.fr> wrote:
>> Why not write in <package>.info:
>>
>> REQUIRES="<some deps> jack1|jack2 <other deps>"
>>
>> A similar syntax is used since ages by slapt-get & friends, just using
>> comma instead of space as token delimiter.
>>
>> I doesn't matter that the vertical line be surrounded by spaces or not,
>> as sbopkg  & friends could remove them with:
>> sed '/REQUIRES/s@[[:space:]]*|[[:space:]]*@|@g' <package>.info
>> or something like that.
>>
>> Didier
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
> 
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>