avant-window-navigator does not run if no composition manager presents in the system. Reproducible: Always Steps to Reproduce: Actual Results: $ avant-window-navigator Error: Screen isn't composited. Please run compiz (-fusion) or another compositing manager.
I guess we could use some kind of virtual but I feel this would be way overkill.
No, it's a purely run-time dependency and putting them all in a virtual would be useless (not to mention almost impossible). The best here IMHO is for the a-w-n ebuild to show a small einfo. Thanks
This may not be an issue with the new a-w-n (0.3.2) since it apparently pops up a message box telling you when there's no compositing manager running.
I don't think a-w-n pops up the message yet before is installed. I believe it would be better to prevent compiling it if no composing manage exists on the pc.
If it's a runtime dependency (and not a build time dependency) then why stop the program installing? It's not possible to tell whether the user's just about to install one afterwards, so you might just end up frustrating the user. Also, we'd then have to maintain a list of compositing window managers which might not get updated at the same time the tree is updated, which would allow for the even more frustrating situation of having a compositing window manager installed but *still* not being allowed to install a-w-n. Die messages for runtimes dependencies are bad. At best you could get away with an ewarn, but you should still allow the compilation and installation...
(In reply to comment #4) > I don't think a-w-n pops up the message yet before is installed. I believe it > would be better to prevent compiling it if no composing manage exists on the > pc. Again, that's wrong (IMHO) because a compositor is a _strictly_ runtime dep. Forcing a compositor in {R,}DEPEND is a _bad_ idea. AWN will be notified if they run it without a compositor. That's more than necessary in my opinion. Thanks
added an ewarn.
