Re: libopenmpt <-> libmodplug compataibility layer

Hi, On 01/01/17 20:11, Stephen Kitt wrote: > On Sun, 01 Jan 2017 18:30:51 +0100, Jonas Smedegaard wrote: >> Quoting James Cowgill (2017-01-01 16:57:17) >>> Are there any opinions about all this? My current thinking is that >>> option 2 is too invasive to be done for stretch (if

Re: libopenmpt <-> libmodplug compataibility layer

On Sun, 01 Jan 2017 18:30:51 +0100, Jonas Smedegaard wrote: > Quoting James Cowgill (2017-01-01 16:57:17) > > Are there any opinions about all this? My current thinking is that > > option 2 is too invasive to be done for stretch (if we want to do it > > at all), but option 1

Re: libopenmpt <-> libmodplug compataibility layer

Quoting James Cowgill (2017-01-01 16:57:17) > Are there any opinions about all this? My current thinking is that > option 2 is too invasive to be done for stretch (if we want to do it > at all), but option 1 might be possible (if it gets through NEW in > time). Deadline for getting through NEW

libopenmpt <-> libmodplug compataibility layer

Hi all, As a bit of background, both libmodplug and OpenMPT are descendants of the original ModPlug Tracker. libmodplug was forked in 1999 using the open-source player components of ModPlug, originally to create an XMMS plugin which could play module music. In 2004 OpenMPT (Open ModPlug Tracker)