Re: [Jack-Devel] The Situation(s) With JACK

  On 01/11/2012 08:04 AM, Paul Davis wrote:
> i can't imagine stephane shipping jackosx or jack for windows without
> the tools, but that doesn't mean they have to come from the same repo
> as the server. on the other hand, i can't imagine any linux packager
> bundling things from a different repo (and maybe version) into the
> same package.
> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
It drives me bonkers the way GNU / Linux devs split things up. LV2 is 
the worst offender I can think of; Dave Robillard's single SVN 
repository is a huge step in the right direction.

I have a radical suggestion: Put everything into one repository. (Except 
it's not *that* radical: the kernel did this a few years ago, putting 
i386 and x86_64 into a single arch tree, x86.)

As a user, I either do svn co / up, or git clone / pull. Which version 
gets compiled becomes a configure-time option:

./waf configure --prefix=/usr --alsa --ffado --version=(1|2)

./waf configure fails if a version is not specified.

(This would mean Jack1 should switch to waf.) If there are apps I don't 
want compiled, then I can specify them just as painfully as with any 
other build system. (Was that zero, one or two hypens? experimental=0? 
Or --no-experimental?)

If this will cause a lot of immediate breakage, then it should be done 
over the weekend of the LAD conference in April. Make it into a big code 
sprint. Whatever coders are there, who haven't hacked on Jack yet, 
should get into the code and see if there's anything they can do to help.

David Nielson

1326295427.6928_0.ltw:2,a <4F0DA975.1020902 at comcast dot net>