| 1 |
On Mon, Jun 05, 2006 at 08:58:46PM +0100, Luis Medinas wrote: |
| 2 |
> Xmms will be removed soon... Lot's of users still use xmms mostly |
| 3 |
> because it has many plugins that others don't. Xmms is still stable but |
| 4 |
> the upstream is dead so it won't take our patchset. In the end of this |
| 5 |
> year i would like to remove xmms and all plugins but before i need to |
| 6 |
> prepare users for this changes and clean some maintainer-wanted bugs for |
| 7 |
> plugins. |
| 8 |
Provide migration options for the plugins - some of the code is out |
| 9 |
there, it's not in the tree yet, three that I actively use are xosd (the |
| 10 |
XMMS plugin is with the xosd package), xmms-realrandom and |
| 11 |
xmms-morestate. |
| 12 |
|
| 13 |
There are SUSE rpms for audacious-xosd, but I haven't found the SRPM or |
| 14 |
other source anywhere. |
| 15 |
|
| 16 |
In the past, the base xmms plugins were all split to be seperate |
| 17 |
packages, could something similar happen with audacious? |
| 18 |
|
| 19 |
It is possible to reduce some of the memory overhead? Comparing a clean |
| 20 |
start of xmms to a clean start of audacious with my playlist takes twice |
| 21 |
as much virt space, and 50% more resident memory - long term the numbers |
| 22 |
look even worse for audacious. |
| 23 |
|
| 24 |
-- |
| 25 |
Robin Hugh Johnson |
| 26 |
E-Mail : robbat2@g.o |
| 27 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives