I vote ogg2 - the fact that it isn't released yet really doesn't matter, as the development SVN is open to everyone and it installs fine without conflicting with ogg1. This email is sort of a moot point as we're already building it into PySoy, but I just wanted it to be out there what my position was.
Eric Arc Riley wrote: > To ogg1 or ogg2, that is the question. > > libogg1 is old, has wasteful memcopies all over it, and is chalked for > obsoletion as soon as libogg2 gets libogg1 compatability bindings written. > > libogg2 is new, very efficient, easier to implement with, but is not released > yet. The API looks similar from the surface but enough has changed to make > migration time consuming, I know from experience (I maintain py-ogg2) that > it's easier to implement in Python. > > My gut says "ogg2 even though it's more work" > > While we can include it in packaged PySoy releases it does mean that all of > us > developers will, for now, need to grab it from http://svn.xiph.org/trunk/ogg2 > > So - what say you? Is this a reasonable thing to expect from us? > _______________________________________________ > PySoy-Dev mailing list > [email protected] > http://www.pysoy.org/mailman/listinfo/pysoy-dev > _______________________________________________ PySoy-Dev mailing list [email protected] http://www.pysoy.org/mailman/listinfo/pysoy-dev
