Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux
> 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 not merge it) and once you are done, merge it to your branch so i know it can be safely merged in the next public update. -- Willy Sudiarto Raharjo signature.asc Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux
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 few of my own (stuff I haven't used recently), but I have some time to do it in the next day or so. > Will all the renaming changes happen automagically in the background > sometime or will maintainers each have to apply them to their own > SlackBuilds? Automagic is the order of the day. The only thing maintainers will want to check is the formatting of their READMEs, if jack-audio-connection-kit is mentioned there (usually as an optional dependency). The replacement name is much shorter, so I'll reflow the text, but everyone should double-check & make sure it looks good to them. I won't be doing it all in one huge commit. Each build will get its own git commit, meaning they can be rolled back or otherwise adjusted without making a mess in the log. > One of my SlackBuilds currently needs updating to a new > version (though not urgently). How to proceed - should I incorporate any > jack related changes now or sit tight? 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. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux
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 from our repo. No hurry on this. > Is there a timetable for this? I've checked all my own relevant SlackBuilds as being OK for the change (and klaatu seems to have already checked most/all others). Will all the renaming changes happen automagically in the background sometime or will maintainers each have to apply them to their own SlackBuilds? One of my SlackBuilds currently needs updating to a new version (though not urgently). How to proceed - should I incorporate any jack related changes now or sit tight? chris ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux
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 >> got this message... >> >> Christoph Willing >> graphics/Blender >> graphics/vsxu >> multimedia/obs-studio >> multimedia/openshot >> multimedia/vlc >> > > OK, I'll check these in the next few days. > All checked OK. chris ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux
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 https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux
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, please let me know you got this message... Got the message. Johannes ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux
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: Felix Pfeifer audio/SuperCollider audio/Pd-extended Michales Michaloudes audio/pd They all work with jack2. For pd/Pd-extended jack is an optional dependency. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux
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 things fail to build, or run >> incorrectly, and you get stuck trying to fix them, contact me by email >> or IRC (freenode, user Urchlay) and I'll attempt to help you out. >> >> 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... Thank you about your care and your solution. (I also prefer jack name over jack-audio-connection-kit) I had a no-go problem (years ago) with jack2 but I don’t remember anything about the problem. I don’t have too much time, but I will try to migrate to jack2 and test my builds. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux
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 version 1 to be archaic, and it'll only be updated if > major issues are discovered (e.g. security fixes). They say nobody should > still be using jack1, and if something that works on jack1 doesn't work > on jack2, that's a bug in jack2 that should be reported. > > 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 from our repo. No hurry on this. > > Why not rename jack2 to jack-audio-connection-kit? Because the switchover > is already going to cause enough confusion without also having the names > clash. Also, upstream refers to it as "jack" these days. > > 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 things fail to build, or run > incorrectly, and you get stuck trying to fix them, contact me by email > or IRC (freenode, user Urchlay) and I'll attempt to help you out. > > 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... > > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ Amazing, I LOVE this solution. Welcome to 2020, JACK. My builds are tested with jack2 as it is, because jack2 is what I run on all of my machines. 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): * Christoph Willing https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] jack-audio-connection-kit vs. jack2, redux
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 > graphics/Blender > graphics/vsxu > multimedia/obs-studio > multimedia/openshot > multimedia/vlc > OK, I'll check these in the next few days. chris ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
