From: Ioannis Aslanidis <aslanidis@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Xmms needs to die.
Date: Wed, 23 Aug 2006 22:47:34 +0200 [thread overview]
Message-ID: <44ECBEE6.8030901@gmail.com> (raw)
In-Reply-To: <1156365020.13743.15.camel@darksytem>
xmms2 and audacious sound good ;)
Luis Medinas wrote:
> Hi everyone.
>
> I'm the current maintainer for xmms and all plugins. As you all know
> xmms is writen over GTK+-1. This toolkit is not supported by the
> upstream like xmms. We have lot's of dead upstream plugins on portage
> and this is a pain to maintain like xmms itself. You might want to look
> at our patchset that contains fixes for 'millions' of bugs.
> We have a few alternatives like audacious, gstreamer based players and
> xine-lib players (did i forget anything ?). The problem is that this
> players doesn't support a few audiotypes or plugins that xmms currently
> does.
> So i'm asking for a solution either remove xmms, move the maintainer for
> anyone who volunteer or the sound herd.
> My plans now is replace xmms for xmms2 (that i would like to take the
> maintainership). Opinions ? Ideas ?
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-23 20:50 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 20:30 [gentoo-dev] Xmms needs to die Luis Medinas
2006-08-23 20:47 ` Ioannis Aslanidis [this message]
2006-08-24 0:07 ` Mike Frysinger
2006-08-24 2:49 ` Luis Medinas
2006-08-24 2:58 ` Alec Warner
2006-08-24 3:11 ` Josh Saddler
2006-08-24 3:32 ` Luis Medinas
2006-08-24 0:00 ` [gentoo-dev] " Christian 'Opfer' Faulhammer
2006-08-24 9:44 ` Luis Medinas
2006-08-24 4:33 ` [gentoo-dev] " Luca Barbato
2006-08-24 13:12 ` Stephen P. Becker
2006-08-24 16:23 ` Dominique Michel
2006-08-24 19:37 ` Luca Barbato
2006-08-24 19:48 ` Stephen P. Becker
2006-08-24 19:57 ` Ciaran McCreesh
2006-08-24 22:41 ` Stephen P. Becker
2006-08-25 14:41 ` bret curtis
2006-08-24 20:07 ` Luca Barbato
2006-08-24 4:44 ` Mike Frysinger
2006-08-24 6:40 ` Richard Fish
2006-08-24 7:01 ` Jakub Moc
2006-08-24 13:34 ` Anders Hellgren
2006-08-24 12:19 ` Robert Cernansky
2006-08-24 13:16 ` Pierre Guinoiseau
2006-08-24 13:53 ` Robert Cernansky
2006-08-24 14:01 ` Krzysiek Pawlik
2006-08-24 14:22 ` Robert Cernansky
2006-08-24 15:08 ` Andrej Kacian
2006-08-24 16:42 ` Robert Cernansky
2006-08-24 16:55 ` Adriaan Leijnse
2006-08-24 17:34 ` Andrej Kacian
2006-08-25 7:03 ` Robert Cernansky
2006-08-27 17:46 ` Doug Goldstein
2006-08-27 20:51 ` Ciaran McCreesh
2006-08-27 21:08 ` Doug Goldstein
2006-08-24 18:46 ` Alec Warner
2006-08-25 7:05 ` Robert Cernansky
2006-08-26 15:04 ` Paul de Vrieze
2006-08-26 17:00 ` Alec Warner
2006-08-26 20:07 ` Luis Francisco Araujo
2006-08-26 17:46 ` Josh Saddler
2006-08-26 18:03 ` Luis Medinas
2006-08-27 8:11 ` Robert Cernansky
2006-08-27 8:26 ` Mike Frysinger
2006-08-27 21:50 ` [gentoo-dev] " Duncan
2006-08-25 9:35 ` [gentoo-dev] " Christian Birchinger
2006-08-25 17:20 ` Steve Dibb
2006-08-25 18:38 ` [gentoo-dev] " Duncan
2006-08-25 20:49 ` [gentoo-dev] " Alec Warner
2006-08-25 20:59 ` Luis Medinas
2006-08-27 8:04 ` Robert Cernansky
2006-08-24 12:21 ` Robin H. Johnson
2006-08-24 10:39 ` Jonathan Adamczewski
2006-08-24 12:31 ` Robert Cernansky
2006-08-24 20:28 ` [gentoo-dev] " Duncan
2006-08-24 10:46 ` [gentoo-dev] " Luis Medinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44ECBEE6.8030901@gmail.com \
--to=aslanidis@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox