Re: [Jack-Devel] lib{j, tsch}ack{, 1, 2} [Was: Jack "capsule/container" implementation?]

PrevNext  Index
DateThu, 10 Feb 2011 20:18:59 +0100
From Dominique Michel <[hidden] at vtxnet dot ch>
To"[hidden] at lists dot jackaudio dot org" <[hidden] at lists dot jackaudio dot org>
In-Reply-Tohermann Re: [Jack-Devel] lib{j, tsch}ack{, 1, 2} [Was: Jack "capsule/container" implementation?]
Le Thu, 10 Feb 2011 19:29:41 +0100,
hermann <[hidden]> a écrit :

> Am Donnerstag, den 10.02.2011, 19:16 +0100 schrieb Dominique Michel:
> > The problem for distros
> > like debian and all the other ones based on deb or rpm packaging, is
> > that it is difficult to make 2 versions of the same program to
> > coexist.
> > This is not a problem with gentoo.
> > 
> > [snip. . . ] The disadvantage
> > is that the user must know what he/she is doing. In other words, the
> > user must take the time to read, understand and follow the docs. 
> 
> When you know what you do, this is also no problem with debian or any
> other distro, . .
> 

I know that, I have been using distros like debian and suse for years.
But the process of using gentoo is a little bit more involved. An user
must understand what stuffs like CFLAGS and march are. I don't have a
programmer background and it took me 2 different gentoo installations
to understand what I can and must do, and what I must not do with
portage. :)

My main point was not this. It was than the difference in jack header
files doesn't matter from a packager (or user) POV. They are installed
into the system and the jack aware applications just compile and work
with any of them. If they don't work, it is not an API or ABI issue, but
a bug somewhere.

-- 
"We have the heroes we deserve."
PrevNext  Index

1297365921.14967_0.ltw:2,a <20110210201859.2ffb9948 at tuxstudio dot homenetwork>