In the xmobar ebuild the flag "with_xft" is disabled, and there is no way to enable it. Reproducible: Always Actual Results: xft support disabled by default Expected Results: The ability of enabling or disabling xft, according to the user's preference.
Same problem with unicode. And it seems to require some haskell package named "utf8-string" in order to support unicode...
See the version in the haskell overlay if you want utf8 or xft support. The utf8-string package is needed for both, but we haven't put it into the official tree yet because it is apparently going to be merged into another package (I can't recall which one) Real Soon Now :s Note also that there appears to be a bug with resource allocation involving xmobar with xft support, where CPU usage gradually goes up to 100% over time. As such, usage of xft support is currently discouraged upstream. For more information on this, see http://code.google.com/p/xmobar/issues/detail?id=11 .
(In reply to comment #2) > See the version in the haskell overlay if you want utf8 or xft support. The > utf8-string package is needed for both, but we haven't put it into the official > tree yet because it is apparently going to be merged into another package (I > can't recall which one) Real Soon Now :s > > Note also that there appears to be a bug with resource allocation involving > xmobar with xft support, where CPU usage gradually goes up to 100% over time. > As such, usage of xft support is currently discouraged upstream. For more > information on this, see http://code.google.com/p/xmobar/issues/detail?id=11 . Ok, thanks for the explanation. Best, Damian.
x11-misc/xmobar-0.9.2-r1 was added to portage tree with depends and a patch, mentioned by ivanm
(In reply to comment #4) > x11-misc/xmobar-0.9.2-r1 was added to portage tree with depends and a patch, > mentioned by ivanm > Oops, perhaps the patch wasn't uploaded. >>> Unpacking xmobar-0.9.2.tar.gz to /var/tmp/portage/x11-misc/xmobar-0.9.2-r1/work * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /usr/portage/x11-misc/xmobar/files/xmobar-0.9.2-* * ( xmobar-0.9.2-* ) * ERROR: x11-misc/xmobar-0.9.2-r1 failed: * Cannot find $EPATCH_SOURCE!
There is a bug about missing patch https://bugs.gentoo.org/show_bug.cgi?id=295176
Thanks for the notice, Man Shankar. Didn't see that bug report as it wasn't assigned to us. Both the unicode and xft issue should be solved now with that new version, patch by Sergei Trofimovich. Please reopen this bug if it didn't solve your issue.
(In reply to comment #7) > Thanks for the notice, Man Shankar. Didn't see that bug report as it wasn't > assigned to us. > > Both the unicode and xft issue should be solved now with that new version, > patch by Sergei Trofimovich. > Please reopen this bug if it didn't solve your issue. > Well, the ebuild isn't pulling the deps. Error output of command `emerge -v xmobar` : ----------------------------------------------- * Applying xmobar-0.9.2-cpu-high-load.patch ... [ ok ] >>> Source unpacked in /var/tmp/portage/x11-misc/xmobar-0.9.2-r1/work >>> Compiling source in /var/tmp/portage/x11-misc/xmobar-0.9.2-r1/work/xmobar-0.9.2 ... * Using cabal-1.6.0.3. [1 of 1] Compiling Main ( /var/tmp/portage/x11-misc/xmobar-0.9.2-r1/work/xmobar-0.9.2/Setup.lhs, /var/tmp/portage/x11-misc/xmobar-0.9.2-r1/work/xmobar-0.9.2/Setup.o ) Linking setup ... Configuring xmobar-0.9.2... setup: At least the following dependencies are missing: X11-xft >=0.2, hinotify -any, parsec -any, stm -any * ERROR: x11-misc/xmobar-0.9.2-r1 failed: * setup configure failed ----------------------- Of course emerging after doing # emerge -v1 dev-haskell/x11-xft hinotify parsec stm works. Interestingly, older ver pulls the deps as usual # emerge -pv =xmobar-0.9 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-haskell/parsec-2.1.0.1 USE="-doc -profile" 0 kB [ebuild N ] dev-haskell/filepath-1.1.0.2 USE="-doc -profile" 0 kB [ebuild N ] dev-haskell/stm-2.1.1.2 USE="-doc -profile" 0 kB [ebuild N ] x11-misc/xmobar-0.9 0 kB Total: 4 packages (4 new), Size of downloads: 0 kB Whats wrong, do you want me to open a new bug?
Man Shankar, thanks again :) There was a mixup of the DEPEND / RDEPEND flags in the ebuild, something you don't notice if you already have all packages installed like I did. It should be fixed now in portage. (In general, new issue -> open new bug)
(In reply to comment #9) > Man Shankar, thanks again :) > There was a mixup of the DEPEND / RDEPEND flags in the ebuild, something you > don't notice if you already have all packages installed like I did. > > It should be fixed now in portage. > (In general, new issue -> open new bug) > Thank you. It is indeed fixed.
