Wait, why is i3-wm both a hard and optional dependency? Pretty sure it's supposed to be optional since polybar works with bspwm as well.
Search Criteria
Package Details: polybar 3.4.0-2
| Git Clone URL: | https://aur.archlinux.org/polybar.git (read-only) |
|---|---|
| Package Base: | polybar |
| Description: | A fast and easy-to-use status bar |
| Upstream URL: | https://github.com/polybar/polybar |
| Keywords: | bar bspwm i3 lemonbar lemonbuddy polybar |
| Licenses: | |
| Conflicts: | |
| Submitter: | jaagr |
| Maintainer: | jaagr (NBonaparte, patrick96) |
| Last Packager: | patrick96 |
| Votes: | 216 |
| Popularity: | 17.400294 |
| First Submitted: | 2016-11-19 05:09 |
| Last Updated: | 2019-07-30 22:51 |
Dependencies (21)
- alsa-lib (alsa-lib-x205ta)
- cairo (cairo-dfb, cairo-minimal, cairo-ubuntu, cairo-glesv2-aarch64, cairo-infinality, cairo-git, cairo-infinality-remix)
- curl (curl-http2-git, curl-git)
- jsoncpp (jsoncpp-git)
- libmpdclient
- libnl (libnl-git)
- libpulse (pulseaudio-git, libpulse-nosystemd)
- xcb-util-cursor (xcb-util-cursor-git)
- xcb-util-image
- xcb-util-wm
- xcb-util-xrm (xcb-util-xrm-git)
- cmake (cmake-git) (make)
- git (git-git) (make)
- i3-wm (i3-kde, i3-gaps-doubleborder, i3-plasma, i3-gaps-fullscreen-next-git, i3-gaps-cameronleger-git, i3-git, i3-gaps-next-git, i3-wm-iconpatch, i3-gaps-rounded-git, i3-gaps) (make)
- pkg-config (pkgconf-git, pkgconf) (make)
- python (python-dbg) (make)
- python2 (pypy19, stackless-python2) (make)
- i3-wm (i3-kde, i3-gaps-doubleborder, i3-plasma, i3-gaps-fullscreen-next-git, i3-gaps-cameronleger-git, i3-git, i3-gaps-next-git, i3-wm-iconpatch, i3-gaps-rounded-git, i3-gaps) (optional) – i3 module support
- siji-git (optional) – Font used in example config
- ttf-unifont (optional) – Font used in example config
- xorg-fonts-misc (xorg-fonts-misc-simple, xorg-fonts-misc-otb) (optional) – Font used in example config
Required by (2)
- leftwm (optional)
- leftwm-git (optional)
Sources (1)
qwertea commented on 2019-09-10 05:51
patrick96 commented on 2019-09-08 06:56
@cobaltspace bdf-unifont is not scalable
cobaltspace commented on 2019-09-07 22:50
What is the reason in optionally requiring ttf-unifont instead of bdf-unifont?
icd_olivia commented on 2019-09-07 17:49
@patrick96 Alright, I'll do as you mentioned. Thanks for your help!
patrick96 commented on 2019-09-07 17:46
@icd_olivia This does look like an issue on our end. Could you head over to our github and create a new issue about this build issue and please also post the entire build log. It will be easier to handle it there.
icd_olivia commented on 2019-09-07 17:39
@patrick96 Thanks for your reply. Sorry for the lack of information regarding my last message. This is what I've got while building the package :
Thanks again for your help!
patrick96 commented on 2019-09-07 16:34
@icd_olivia If you get a segfault while building, it's likely an issue with your build tools and not polybar. If you post the exact errors and warnings, we might be able to better help you.
icd_olivia commented on 2019-09-05 23:49
I'm getting an error while building the packages, same goes for the git one (Seg fault).
dctxmei commented on 2019-08-01 03:09
@patrick96 I checked the new PKGBUILD, which is very satisfying.
Thanks for your efforts, I will remove the polybar-full package.
patrick96 commented on 2019-07-31 09:41
@1ace The last commit didn't introduce any new hard x11 dependencies and i3 is still an optdepends. Also, polybar doesn't even compile without xcb-util-wm and xcb-util-image. And the other two aren't really optional dependencies, once polybar is compiled with them, they cannot be uninstalled.
@dctxmei Pushed the new PKGBUILD btw.
Pinned Comments
TheGreatAndyChow commented on 2019-04-23 03:46
For problems with conda, simply "conda deactivate", it will install. No need to purge path or remove anaconda.