Package Details: polybar-git 3.6.3-1

Git Clone URL: https://aur.archlinux.org/polybar-git.git (read-only, click to copy)
Package Base: polybar-git
Description: A fast and easy-to-use status bar
Upstream URL: https://github.com/polybar/polybar
Keywords: bar bspwm i3 lemonbar lemonbuddy polybar
Licenses: MIT
Conflicts: polybar
Provides: polybar
Submitter: jaagr
Maintainer: jaagr (NBonaparte, patrick96)
Last Packager: patrick96
Votes: 53
Popularity: 0.001462
First Submitted: 2016-11-19 05:07 (UTC)
Last Updated: 2022-05-04 09:21 (UTC)

Required by (10)

Sources (1)

Pinned Comments

patrick96 commented on 2021-12-28 15:29 (UTC)

I went ahead and added aarch64 as an architecture to the PKGBUILD.

Please be aware that polybar is not maintained on aarch64 and there is no official support for it (even if it will probably run fine). We do our best to get it to compile on ARM and do accept patches for that, but for any ARM-related runtime issues we cannot provide proper support because we don't have access to aarch64 machines.

Latest Comments

1 2 3 4 5 Next › Last »

patrick96 commented on 2022-04-30 20:42 (UTC)

@cysp74 Thanks! Added it to both packages. I just assumed pacman automatically does this for files in /etc

cysp74 commented on 2022-04-30 17:54 (UTC)

Hey,

Just dropping here a small patch for creating backup of existing config files upon upgrading package.


diff --git a/PKGBUILD b/PKGBUILD
index 9663eb4..cdf185e 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,7 +1,7 @@
 # Maintainer: Patrick Ziegler <p.ziegler96@gmail.com>
 _pkgname=polybar
 pkgname="${_pkgname}-git"
-pkgver=3.6.2
+pkgver=3.6.2.r36.g6a2d7b5d
 pkgrel=1
 pkgdesc="A fast and easy-to-use status bar"
 # aarch64 is not officially supported by polybar, it is only listed here for convenience
@@ -12,6 +12,7 @@ depends=("libuv" "cairo" "xcb-util-image" "xcb-util-wm" "xcb-util-xrm"
          "xcb-util-cursor" "alsa-lib" "libpulse" "libmpdclient" "libnl"
          "jsoncpp" "curl")
 optdepends=("i3-wm: i3 module support")
+backup=(etc/polybar/config.ini)
 makedepends=("cmake" "git" "python" "pkg-config" "python-sphinx"
              "python-packaging" "i3-wm")
 provides=("polybar")

patrick96 commented on 2021-12-28 15:29 (UTC)

I went ahead and added aarch64 as an architecture to the PKGBUILD.

Please be aware that polybar is not maintained on aarch64 and there is no official support for it (even if it will probably run fine). We do our best to get it to compile on ARM and do accept patches for that, but for any ARM-related runtime issues we cannot provide proper support because we don't have access to aarch64 machines.

patrick96 commented on 2021-09-04 13:09 (UTC)

@nem Removing those dependencies will build polybar without i3 or mpd support. The goal of this package is to produce a fully-featured polybar.

nem commented on 2021-07-19 11:54 (UTC)

Removing "libmpdclient" from "depends" as well as removing "i3-wm" from "makedepends" will build and run polybar with exmaple config without issues. They should be removed from the PKGBUILD and should not be hard dependencies there.

patrick96 commented on 2020-07-13 21:57 (UTC)

@TrueBers Don't use the mpd module if you don't want polybar to try to connect to mpd. libmpd cannot be an optional dependency, polybar's optional dependencies are only optional at compile-time, at runtime most of them are mandatory if polybar was compiled with that feature.

TrueBers commented on 2020-07-13 13:39 (UTC)

Shouldn't libmpd be an optional dependency as it's stated on Github? It's bashing mpd socket every second which is very annoying.

jameh commented on 2020-05-17 00:55 (UTC) (edited on 2020-05-17 00:59 (UTC) by jameh)

ah - I realized that polybar -vvv doesn't use the proper release number, but g5cd7295a is indeed the latest commit... EDIT: gotcha - looking forward to 3.5 :D

patrick96 commented on 2020-05-17 00:55 (UTC)

@jameh That's how non-release commits are versioned unfortunately. 3.4.0-106-g5cd7295a is newer than 3.4.3. The master branch where git describe gets the version information doesn't know about patch releases (3.4.X), it only knows about minor releases (3.X.0).

But we want to adapt a different branching scheme in 3.5.0, so that this doesn't happen anymore.