On Thu, Oct 28, 2004 at 03:37:48PM -0400, John (J5) Palmieri wrote:
I hadn't gotten to the point of looking at the code yet. I was
make some test packages, see how it worked as an esd replacement and
then go ahead and start looking at it. If it is as you say,
How can you make packages without reading the code, you don't know if it
contains code to attack Red Hat unless you read it first..
impenetrable spaghetti, then I don't want to gain yet another
unmaintainable package. Is it your position that the things that are
Take a look see what you think. Second opinions are always good
wrong with Polyaudio would be harder to fix than just fixing esd?
perhaps there are better alternatives around? If we can find a solution
that is easy to integrate, maintain and audit I am all for that.
There are several alternative sound servers such as arts (which we already
ship) and lots of fun politics around some of them