16 Apr
2010
16 Apr
'10
3:11 p.m.
Am Freitag, den 16.04.2010, 18:52 +0200 schrieb Ralf Mardorf:
torbenh wrote:
For me this will be an advantage, because now I need to build several
dummy packages (or any other dirty solution) for jack, libjack,
development to avoid inconsistencies when I'm using JACK2 and by the
way, even if I would use JACK1, but instead of the distro's version the
current self compiled version, I need to do that, because auto-generated
by checkinstall there will be one package for jack, libjack and
development ;).
IMO the user should have the choice between JACK1 and JACK2 and this
separated packages should become one package. JACK isn't an application
that's needed by the averaged Linux user, so it shouldn't be to much
work to keep a distro stable for both versions of JACK and in addition
there's no need to take care about rules that don't allow to have jack
and libjack in one package.
2 cents,
Ralf
I hope, when debian switch to jack2, they will make it in one packet
(maximal a second for the dev files), that's what could make it easer to
switch the version for people how like to switch.
+ 2 cents
hermann
Also note
that there's no (easy) way back, we're entirely switching to
jackd2, that is, the user won't have the possibility to select jackd1
instead.
great... many thanks. :(((((((