Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 May 2021 02:17:03 +0200
From:      Florian Walpen <dev@submerge.ch>
To:        multimedia@freebsd.org
Subject:   Re: audio/jack labelled as RC1?
Message-ID:  <1799733.vR5SVPPSqJ@z800>
In-Reply-To: <c008edf8-e98e-d8f7-9219-ef0d18dd3153@selasky.org>
References:  <73fca66a-af4b-01eb-747d-bec8830b5f63@mailo.com> <c008edf8-e98e-d8f7-9219-ef0d18dd3153@selasky.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, May 17, 2021 12:22:24 AM CEST Hans Petter Selasky wrote:
> On 5/13/21 8:43 PM, bsduck@mailo.com wrote:
> > Hello,
> > 
> > I'm trying to build https://rdio.space/jackmixer/ but meson complains
> > about the installed jack version being 0.125.0rc1 while 0.125.0 is
> > 
> > required:
> >> Dependency jack found: NO found 0.125.0rc1 but need: '>=0.125.0, <1.0'
> > 
> > [...]
> > 
> >> meson.build:24:4: ERROR: Problem encountered: No recent enough
> >> (jack2>=1.9.11 or jack1>=0.125.0) version of JACK found.
> > 
> > Isn't the jack port supposed to be version 0.125.0 proper rather than a
> > release candidate? Why does it appear as RC1?
> > My ports are up to date tracking 2021Q2.

Current jack port uses a commit from the jack1 master branch, long after the 
0.125.0 release tag. But it looks like the release number was not updated from 
0.125.0rc1 to 0.125.0 until the following commit in the master branch:

https://github.com/jackaudio/jack1/commit/
0cb641ba3f205f210ed7574e4e5cbf37829dfe89

Apart from updating the port, the quick and dirty way would be to just patch 
the release number in the configure.ac file. The sources are post 0.125.0 
release anyway.

> 
> I think someone is working on jack2 support for FreeBSD.
> 
> --HPS

Yes, still on that mission. But that's not a short term solution.

Florian Walpen





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1799733.vR5SVPPSqJ>