> 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
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
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
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
>>
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
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,
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:
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
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
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
>
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
On 05/29/2015 10:16 AM, Ryan P.C. McQuen wrote:
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
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
On 5/28/15, Klaatu kla...@straightedgelinux.com wrote:
1. list both jack;audio-connection-kit and jack2 in the README file if
your package requires JACK
Kinda annoying if neither one is in REQUIRES in the .info file, it would
break sbotools or sqg's queue building.
2. re-structure the
On 05/28/2015 06:56 AM, Klaatu wrote:
1. list both jack;audio-connection-kit and jack2 in the README file if
your package requires JACK
or...
2. re-structure the jack-audio-connection-kit and jack2 scripts such
that they become one and the same script, by which the user can choose
to
On 05/28/2015 08:14 PM, David Spencer wrote:
2. re-structure the jack-audio-connection-kit and jack2 scripts such
that they become one and the same script, by which the user can choose
to build either jack1 or jack2, depending on their requirements.
What would be in DOWNLOAD= and VERSION=?
IMHO I don't see a reason to merge both into one SlackBuild.
I would say that JACK users are well aware that two versions exist and
this is also a decision from the upstream maintainers and those who
don't use JACK won't use it as it is may just a hard dependency from the
maintainer.
Also,
On 05/28/2015 06:54 PM, B Watson wrote:
On 5/28/15, Klaatu kla...@straightedgelinux.com wrote:
1. list both jack;audio-connection-kit and jack2 in the README file if
your package requires JACK
Kinda annoying if neither one is in REQUIRES in the .info file, it would
break sbotools or sqg's
I think in the future, I'll use %README% in REQUIRES to alert the user
that the version of JACK is optional.
%README% is used to tell users that a package is conflicting/replacing
Slackware packages. Other than that, users are always assumed to read
README.
--
Willy Sudiarto Raharjo
On Thu, 28 May 2015 22:05:51 +1200
Klaatu kla...@straightedgelinux.com wrote:
On 05/28/2015 08:14 PM, David Spencer wrote:
2. re-structure the jack-audio-connection-kit and jack2 scripts
such that they become one and the same script, by which the user
can choose to build either jack1 or
Just thinking out loud... You could have the separate scripts for jack1
and jack2 with their associated .info files set up as dependencies of
a jack-common (or whatever) build script which requires an argument to
select the version desired. Perhaps build information could be passed
via
On 05/29/2015 12:20 AM, Willy Sudiarto Raharjo wrote:
I think in the future, I'll use %README% in REQUIRES to alert the user
that the version of JACK is optional.
%README% is used to tell users that a package is conflicting/replacing
Slackware packages. Other than that, users are always
On May 28, 2015 9:03 AM, Klaatu kla...@straightedgelinux.com wrote:
On 05/29/2015 12:20 AM, Willy Sudiarto Raharjo wrote:
I think in the future, I'll use %README% in REQUIRES to alert the user
that the version of JACK is optional.
%README% is used to tell users that a package is
Is there currently a way to indicate that two packages are able to
satisfy one dependency?
I can't even think of an SBo precedence to base a resolution upon.
I would suggest put one of them as default dependency and list the other
one in README.
That's what i did with your aj-snapshot
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
25 matches
Mail list logo
