ebuilds for libvorbis and vorbis-tools 1.1.1 release (http://lists.xiph.org/pipermail/vorbis-dev/2005-June/018105.html) Reproducible: Always Steps to Reproduce:
and please update for the lastest aotuv patch http://www.geocities.jp/aoyoume/aotuv/
With this patch I'd really like to see something like: "aoTuV beta-3 patched" ...to the output of what libvorbis returns when called about version information. I believe it is important for a user to be able to know what encoder they are using, and to be able to accurately pull that information inside the "user-space". Also there should be a way for software to call oggenc or libvorbis and be able to pull accurate encoder information that way too. Currently I have a piece of software that I maintain that calls: oggenc --version ...to get encoder information. Currently the only output this returns, with the aotuv flag turned on and libvorbis patched, is this: OggEnc v1.0.1 (libvorbis 1.0.1) This is misleading, as libvorbis has been aoTuV patched. However any user or software will be none-the-wiser. In fact the only way to even tell that the encoder has the patch is by listening test or something. Anyway a message included in the aoTuV libvorbis patch would be useful and appropriate. Thank you, Charlton
"2005/07/07 The aoTuV beta4 merged libVorbis 1.1.1." [http://www.geocities.jp/aoyoume/aotuv/]
Created attachment 65688 [details] ebuid for libvorbis-1.1.1 Tested on amd64
Created attachment 65689 [details] ebuild for vorbis-tools-1.1.1 Tested on amd64
Created attachment 65725 [details, diff] aotuv-beta4 patch against libvorbis 1.1.1 Here's the patch for aoTuV beta4 against libvorbis-1.1.1 (aoTuV has not been merged with libvorbis-1.1.1, Aoyumi only provides a merged tarball on his site). Copy the current 1.1.0 ebuild to 1.1.1 and edit it for the aotuv-b4 patch.
It seems that the libvorbis-1.1.1 and the vorbis-tools-1.1.1 are now in portage.
I asked aoyumi to put a patch on his site and he did. Would be nice if libvorbis gets the aotuv use flag again. It would also be nice if a useflag for "lancer" sse flag would be included, see: http://homepage3.nifty.com/blacksword/ (Beware: gcc 3.4 is broken, so won't work with it. Works fine withh gcc 3.3 and 4.0, though).
