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

On Wed, Jan 11, 2012 at 02:33:30PM +0100, Adrian Knoth wrote:
> On 01/11/2012 01:42 PM, Paul Davis wrote:
>
>> so please comment: what is the best way to put the header files that
>> define the JACK API, along with the source code for the
>> example+utility clients somewhere that any implementation of the API
>> could use them?
>
> I'm also not a big fan of submodules. How about the following:
>
>
>    jack-common --> independent repo
>      + headers --> branch in jack-common with the header files
>      + tools
>      + example-clients
>      + manpages
>
> The last three are also branches of the jack-common repo.
>
> The real jackd repositories:
>
>    jackd1   --> independent repo
>    jackd2   --> independent repo
>
> It doesn't really matter if it's one repo with two branches or two
> repos, but I guess the latter is more convenient to use. Correct me if
> I'm wrong.
>
> The jackd developer would now and then do
>
>    $ git pull jack-common headers
>
> to update their *local copy* of header files the current trunk (master)
> is based on.
>
> Same for example-clients, tools and the lot. It's not even necessary
> those things reside on different branches, but it gives the jackd
> developer the opportunity to update example-clients, tools, headers and
> man pages individually (no idea if this is required).

I'd completely split off the example clients and tools: if these are apps
they should be compiled *as applications*, that is using the installed
headers instead of those from the repo, and have their own manpages.

Also manpages for the server could be different for jack1 and jack2 so
these probably belong with their own version and not in common.

That leaves just the headers and the API docs in the common repo.

Ciao,

-- 
FA

Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.

1326289512.29625_0.ltw:2,a <20120111134452.GC31338 at linuxaudio dot org>