[icecast] version confusion

[Brendan Cully]

You're right, the "version issue" is a mess. But it should be
considerably improved within the next few days. Barring surprises,
libshout 2.0 will be officially released Monday (including perl and
python bindings).

At the same time, ices 0.3 will be released, which does compile with
libshout 2.0 (and features a million bug fixes over ices 0.2.3). The
snapshots in http://xiph.org/~brendan/snapshots/ices have built
against the libshout 2 snapshots for quite some time.

ices2 will build against the released libshout 2.0. It will also build
against a libshout 2.0 snapshot as recent as itself.

I don't know when ices2 or icecast 2 will be released, but I am
confident they will build with the released versions of the libraries.

I apologise for the confusion, and hope this helps.

-b

On Friday, 11 July 2003 at 17:50, Guillaume Rousse wrote:
> Hello.
> 
> I'm one of the maintainer of ices packages found at http://plf.zarb.org. I'm 
> currently trying to rebuild the whole ice/icecast/libshout trilogy. However, 
> i'm running into some troubles.
> 
> From what i understand, the old suite is ices 0.2.3 , icecast 1.3.12 and 
> libshout 1.0.8. The new suite has only tagged release for libshout 2.0 beta3, 
> whereas everything else is CVS snapshot.
> 
> Various compilation attempt showed me that libshout 1 is unusable with icecast 
> 2, that ices 0.2.3 doesn't build with libshout 2 (not suitable libshout found 
> in configure stage, with many pthread related error messages in 
> configure.log), and that latest ices2 snaphosts doesn't build either against 
> libshout2 (this libshout is not thread-safe).
> 
> So, i guess the best strategy is still currently stand with old version for 
> everything, until there is at least tagged beta release available for 
> everything in new suite. Am i correct ?
--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to 'icecast-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.