| 1 |
On Thu, 2006-06-08 at 01:30 -0700, Robin H. Johnson wrote: |
| 2 |
> On Mon, Jun 05, 2006 at 08:58:46PM +0100, Luis Medinas wrote: |
| 3 |
> > Xmms will be removed soon... Lot's of users still use xmms mostly |
| 4 |
> > because it has many plugins that others don't. Xmms is still stable but |
| 5 |
> > the upstream is dead so it won't take our patchset. In the end of this |
| 6 |
> > year i would like to remove xmms and all plugins but before i need to |
| 7 |
> > prepare users for this changes and clean some maintainer-wanted bugs for |
| 8 |
> > plugins. |
| 9 |
> Provide migration options for the plugins - some of the code is out |
| 10 |
> there, it's not in the tree yet, three that I actively use are xosd (the |
| 11 |
> XMMS plugin is with the xosd package), xmms-realrandom and |
| 12 |
> xmms-morestate. |
| 13 |
> |
| 14 |
> There are SUSE rpms for audacious-xosd, but I haven't found the SRPM or |
| 15 |
> other source anywhere. |
| 16 |
> |
| 17 |
Yes we will provide migrations to the plugins. Audacious is currently |
| 18 |
the only player on the tree that supports xmms plugins. Maybe it's time |
| 19 |
to develop some plugins or start packaging. |
| 20 |
|
| 21 |
> In the past, the base xmms plugins were all split to be seperate |
| 22 |
> packages, could something similar happen with audacious? |
| 23 |
> |
| 24 |
> It is possible to reduce some of the memory overhead? Comparing a clean |
| 25 |
> start of xmms to a clean start of audacious with my playlist takes twice |
| 26 |
> as much virt space, and 50% more resident memory - long term the numbers |
| 27 |
> look even worse for audacious. |
| 28 |
> |
| 29 |
Ask Audacious upstream but since it's build with gtk+-2 you can find it |
| 30 |
a little bit slower. |
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-dev@g.o mailing list |
Archives