Re: [RFC] Release news entry and download page changes
Reimar Döffinger <Reimar.Doeffinger <at> gmx.de>
2012-06-10 15:48:49 GMT
On Fri, Jun 08, 2012 at 01:03:10PM +0100, Andy Furniss wrote:
> Thomas Orgis wrote:
> >Am Thu, 07 Jun 2012 21:59:57 +0100
> >schrieb Andy Furniss <andyqos <at> ukfsn.org>:
> >>Reimar Döffinger wrote:
> >>>Also the internal mp3lib copy is no
> >>>+longer used by default, also because the codebase has often show issues with the
> >>>+newest compilers. However it is still selectable at runtime by default.
> >>>+If you do not actually need it consider disabling it at compile time with --disable-mp3lib.
> >>Doesn't read too well.
> >>Is the issue with new compilers at run time or a build fail?
> >AFAIK, it was build failure. Is there a specific reason that you would
> >rather rely on the mp3lib fork of mpg123 code (some time ago, it was)
> >instead of the libmpg123 binding that replaces it? Also, there is the
> >mp3 decoder in ffmpeg. So, MPlayer doesn't loose functionality here,
> >just code that needed extra maintenance.
> Sorry for any confusion, I should have replied to Alexander.
> My question was to do with his request for a native English speaker
> to look over the wording.
> Anyway given you answer, here's how I would word it.
> The internal mp3lib copy is no longer used by default, but it is