Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#23485 - [avant-window-navigator] Contains unnecessary dependencies.

Attached to Project: Community Packages
Opened by Filipp Andjelo (scorp) - Monday, 28 March 2011, 21:32 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 14 December 2011, 18:15 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Since version 0.4.0, avant-window-navigator uses desktop-agnostic instead of gconf. It's a frontend for configuration backend and vfs. There is no dependency of gconf anymore and AWN can now be used on very lightweight systems without gconf too! desktop-agnistic would just save configuration in a ini-like file under $HOME/.config directory.

Additional info:
* package version(s)
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Wednesday, 14 December 2011, 18:15 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Moved to AUR
Comment by Jelle van der Waa (jelly) - Tuesday, 29 March 2011, 22:25 GMT
* GNU Make
* libdesktop-agnostic [1]_
* libwnck 2.22 or later
* libX11
* dbus-glib
* xdamage
* xcomposite
* xrender
* Python 2.5 or later
* PyGTK 2.12 or later
* pyxdg (also known as python-xdg)
Comment by Jelle van der Waa (jelly) - Tuesday, 29 March 2011, 22:30 GMT
when trying to compile it, it says it needs gconf, i don't think you can disable it.
Nevermind: --without-gconf exists
Comment by Filipp Andjelo (scorp) - Wednesday, 30 March 2011, 10:28 GMT
I made already a custom PKGBUILD for it and it works fine without gconf at all. You'll need gconf in makedepends, but not in depends. There is still a problem with installation script used in PKGBUILD, where gconf is used to install schemes. The awn runtime itself uses desktop-agnostic later to handle it's configuration. If gconf should be used behind it, then the installed schemes are needed.
You can take a look at this dependency matrix(look at footnotes too):

We have to think about how to get gconf schemes problem solved, since if you would want to install gconf after awn, then the schemes would be unknown and desktop-agnostic wouldn't know how to get configuration data for awn.