Information for Polybar Package Maintainers

[patrick96]

If you want to create a polybar package for your distro, please read this page in our documentation.

If you are already maintaining a polybar package in some distro, please subscribe to this thread.

We will post a comment here whenever there is a new release and we will also include anything that has changed for building and packaging the new version.

This thread is not intended for discussions of new releases, please do not comment here, we don't want to spam people that have subscribed to this thread. If you have any issues or questions about packaging the new release, please open a new issue (or ask on Gitter).

[patrick96]

We have released polybar 3.4.2 🚀

There are no changes to the build workflow.

Build issues on the new gcc10 have been fixed.

[patrick96]

We have released polybar 3.4.3 🚀

This release only contains a fix for a gcc10 build issue (#2098).

[patrick96]

We have just released polybar 3.5.0 🎉

Packaging-wise not much has changed. You can now specify the python executable to use during compilation by passing -D:PYTHON_EXECUTABLE=/path/to/python to cmake, though for packaging this shouldn't really be necessary, it's more for systems that have conda or pyenv.

The bigger change is probably that the i3ipcpp submodule now doesn't compile jsoncpp itself, it just always uses whatever jsoncpp is available (we have not yet had problems with jsoncpp < 1.7.7).

[patrick96]

The first patch release for 3.5 is out now: polybar 3.5.1 🚀

From now on, the release archive is a .tar.gz file instead of just a tar file and it contains a folder named polybar-<version> instead of just polybar.

We also fixed some build issues in older clang versions (3.4) and some in more modern clang.

[patrick96]

Polybar 3.5.2 is out now.

Just a quick bugfix, no build changes.

[patrick96]

Just released version 3.5.3.

This fixes the issue where you needed to have git installed to build the documentation even if you were building from a release archive.

[patrick96]

3.5.4 is out now, there were no build changes.

[patrick96]

We just released 3.5.5. There was a build issue with older python-sphinx versions that is now fixed.

[patrick96]

I just published version 3.5.6

The documentation should now also build with sphinx 4 and we fixed a crash with the i3 module which affected the AUR packages as well as I think Fedora.

[patrick96]

Polybar 3.5.7 is out now.

There should be no changes that affect packaging.

[patrick96]

Version 3.6.0 is finally out now 🚀

There have been a bunch of changes to the build system. I'll list the most important ones here, find the full list on the release page.

• Installed components (docs, shell completion, binaries, etc.) can be enabled and disabled separately
• You can no longer configure the doc directory. Documentation-only builds are now possible when configuring the repo root directory
• New dependency: libuv. At least version 1.3 is required.
• New minimal cmake version: 3.5
• Polybar installs a default config to /etc/polybar/config.ini

[patrick96]

I just published 3.6.1.

It fixes a bunch of build issues, especially with newer compilers.

Thank you for reporting these kinds of issues so quickly 😃

[patrick96]

Version 3.6.2 is out now.

No build changes, but there are a bunch of important bug fixes.

[patrick96]

3.6.3 is finally out.

No changes to the build system again, only bug fixes.

[patrick96]

Polybar 3.7.0 has just been released.

There were a few changes that may be relevant for packagers:

• Files are installed to /usr by default instead of /usr/local.
• We respect CMAKE_INSTALL_PREFIX when installing the default config (this should fix gentoo builds). We still install to /etc/polybar/config.ini, but now use CMake's CMAKE_INSTALL_SYSCONFDIR value.
• The C++ version for the project is now C++17 and thus needs a C++17 capable compiler. From my investigations those should be either gcc8+ or clang7+

[patrick96]

Version 3.7.1 was just released. It includes a patch to fix builds in older clang versions.