Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux

2020-01-17 Thread Willy Sudiarto Raharjo
> Go ahead and submit it as-is (listing jack-audio-connection-kit in > REQUIRES), if you're ready to. I will wait until Willy's regular weekly > update is done, before making any changes. You can start in a separate branch and mark it as nomerge (or other names that clearly state that i should

Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux

2020-01-16 Thread B Watson
On 1/16/20, Christoph Willing wrote: > > Is there a timetable for this? Probably over the weekend, with final update Sunday or possibly Monday. I had thought it would take longer since there are so many builds, but apparently I'm not the only one who quietly upgraded to jack2. I want to check a

Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux

2020-01-16 Thread Christoph Willing
On 15/1/20 8:16 am, B Watson wrote: > > So I propose to do this: > > - Rename jack-audio-connection-kit to jack1-legacy. > - Rename jack2 to jack. > - Update all .info files and READMEs that mention jack-audio-connection-kit, > so they say "jack" instead. > - Eventually, get rid of jack1-legacy

Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux

2020-01-16 Thread Christoph Willing
On 15/1/20 8:30 am, Christoph Willing wrote: > On 15/1/20 8:16 am, B Watson wrote: >> >> Here's a list of all the builds that currently depend on >> jack-audio-connection-kit (REQUIRES or mentioned in the README), broken >> out by maintainer. If your name is on this list, please let me know you >>

Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux

2020-01-15 Thread Dave Woodfall
On 2020-01-14 17:16, B Watson put forth the proposition: > David Woodfall > audio/lash Will do. -daw signature.asc Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org

Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux

2020-01-15 Thread Franzen
Hi, - Update all .info files and READMEs that mention jack-audio-connection-kit, so they say "jack" instead. .. and make jack2 saying jack also. I did some testing a while ago, consider my builds working with jack2, i'll tell if i find issues with jack2. If your name is on this list,

Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux

2020-01-15 Thread Felix Pfeifer
On 1/14/20 11:55 PM, Klaatu wrote: ... > I have also tested, extensively, these applications with jack2 (by running > them on either my computer or computers I maintain for band mates and > collaborators): ... > * Felix Pfeifer * audio/muse > Thanks for testing! I tested these:

Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux

2020-01-14 Thread Μιχάλης Μιχαλούδης
15 Ιαν 2020, 12:55 πμ, ο χρήστης «Klaatu » έγραψε: >> On Tuesday, January 14, 2020 05:16:35 PM B Watson wrote: >> >> Maintainers of builds that depend on jack-audio-connection-kit, you >> can help by installing jack2 (instead of jack-audio-connection-kit) >> and testing your builds with it. If

Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux

2020-01-14 Thread Klaatu
On Tuesday, January 14, 2020 05:16:35 PM B Watson wrote: > So I've been thinking about this, and talking to upstream JACK > developers... > > We current have jack-audio-connection-kit (JACK version 1.x) and jack2 > (version 2.x). I maintain both builds these days... > > Upstream considers

Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux

2020-01-14 Thread Christoph Willing
On 15/1/20 8:16 am, B Watson wrote: > > Here's a list of all the builds that currently depend on > jack-audio-connection-kit (REQUIRES or mentioned in the README), broken > out by maintainer. If your name is on this list, please let me know you > got this message... > > Christoph Willing >

[Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux

2020-01-14 Thread B Watson
So I've been thinking about this, and talking to upstream JACK developers... We current have jack-audio-connection-kit (JACK version 1.x) and jack2 (version 2.x). I maintain both builds these days... Upstream considers version 1 to be archaic, and it'll only be updated if major issues are