FS#24576 - Audacious Should Use GTK3

Attached to Project: Arch Linux
Opened by Alex Charron (RetroX) - Saturday, 04 June 2011, 17:41 GMT
Last edited by Gaetan Bisson (vesath) - Sunday, 05 June 2011, 23:12 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Currently, the audacious package in [extra] depends on GTK 2, even though audacious does have a GTK 3 port.

I don't know if it's necessarily the best choice to make this the default, but I still think that there should be an option for the gtk3 port. Maybe separate audacious-gtk2 and audacious-gtk3 packages? If there is currently support for both, I don't see why both can't be included.
This task depends upon

Closed by  Gaetan Bisson (vesath)
Sunday, 05 June 2011, 23:12 GMT
Reason for closing:  Deferred
Comment by Gaetan Bisson (vesath) - Sunday, 05 June 2011, 23:11 GMT
Currently there are still a few bits of audacious that are not gtk3-compatible, namely the plugins adplug, alarm, aosd, evdev-plug, jack, ladspa, lirc, modplug, moodbar, paranormal, projectm-1.0, sid, skins, spectrum, and streambrowser. So for the time being, it is best to stick to gtk2.
We cannot possibly package every program with each dependency combination in the official repositories, but you are free to package your own audacious-gtk3 using the ABS and/or maintain it in the AUR.

Loading...