Bug 722544 - FutureFeature for audacious-plugins-exotic
Summary: FutureFeature for audacious-plugins-exotic
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: audacious-plugins
Version: 15
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Michael Schwendt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-15 15:39 UTC by Jarrod Makin
Modified: 2011-07-15 16:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-15 16:10:43 UTC
Type: ---


Attachments (Terms of Use)

Description Jarrod Makin 2011-07-15 15:39:41 UTC
Could a future version of audacious-plugins-exotic incorporate the vgmstream code at http://sourceforge.net/projects/vgmstream/

It supports a wide range of videogame input formats that would compliment the selection already available.

Comment 1 Michael Schwendt 2011-07-15 16:10:43 UTC
audacious-plugins-exotic only includes some plugins from the official audacious-plugins distribution, as explained in the package description.

[...]

For vgmstream and its Audacious plugin to enter Fedora's package collection, somebody would need to push it through the http://fedoraproject.org/wiki/Package_Review_Process and become the package maintainer of it.

Alternatively, you could approach the http://audacious-media-player.org/ developers (e.g. in the forums) and ask whether they might want to include a plugin for a vgmstream library. Then a vgmstream library package would still need to enter the Fedora package collection before it could be used when compiling audacious-plugins.

A simple build attempt of vgmstream-r659 fails:

  checking for AUDACIOUS... yes
  checking for VORBISFILE... yes
  checking for MPG123... no
  configure: error: Cannot find libmpg123

That's a hard requirement, which cannot enter Fedora:
http://fedoraproject.org/wiki/Forbidden_items#MP3_Support

Further, the Audacious Plugin API has changed heavily since 2010, so the included plugin which targets "audacious >= 1.4.0" possibly doesn't compile anymore and will need a lot of fixes and active developers. Last vgmstream release is from 2009, however, afaics.


Note You need to log in before you can comment on or make changes to this bug.