yambar: init at 1.6.1
This commit is contained in:
parent
19a714d431
commit
6a7e9f3e11
2 changed files with 88 additions and 0 deletions
86
pkgs/applications/misc/yambar/default.nix
Normal file
86
pkgs/applications/misc/yambar/default.nix
Normal file
|
@ -0,0 +1,86 @@
|
|||
{ stdenv
|
||||
, lib
|
||||
, fetchgit
|
||||
, pkg-config
|
||||
, meson
|
||||
, ninja
|
||||
, scdoc
|
||||
, alsaLib
|
||||
, fcft
|
||||
, json_c
|
||||
, libmpdclient
|
||||
, libxcb
|
||||
, libyaml
|
||||
, pixman
|
||||
, tllist
|
||||
, udev
|
||||
, wayland
|
||||
, wayland-protocols
|
||||
, xcbutil
|
||||
, xcbutilcursor
|
||||
, xcbutilerrors
|
||||
, xcbutilwm
|
||||
}:
|
||||
|
||||
stdenv.mkDerivation rec {
|
||||
pname = "yambar";
|
||||
version = "1.6.1";
|
||||
|
||||
src = fetchgit {
|
||||
url = "https://codeberg.org/dnkl/yambar.git";
|
||||
rev = version;
|
||||
sha256 = "p47tFsEWsYNe6IVV65xGG211u6Vm2biRf4pmUDylBOQ=";
|
||||
};
|
||||
|
||||
nativeBuildInputs = [ pkg-config meson ninja scdoc ];
|
||||
buildInputs = [
|
||||
alsaLib
|
||||
fcft
|
||||
json_c
|
||||
libmpdclient
|
||||
libxcb
|
||||
libyaml
|
||||
pixman
|
||||
tllist
|
||||
udev
|
||||
wayland
|
||||
wayland-protocols
|
||||
xcbutil
|
||||
xcbutilcursor
|
||||
xcbutilerrors
|
||||
xcbutilwm
|
||||
];
|
||||
|
||||
meta = with lib; {
|
||||
homepage = "https://codeberg.org/dnkl/yambar";
|
||||
description = "Modular status panel for X11 and Wayland";
|
||||
longDescription = ''
|
||||
yambar is a lightweight and configurable status panel (bar, for short) for
|
||||
X11 and Wayland, that goes to great lengths to be both CPU and battery
|
||||
efficient - polling is only done when absolutely necessary.
|
||||
|
||||
It has a number of modules that provide information in the form of
|
||||
tags. For example, the clock module has a date tag that contains the
|
||||
current date.
|
||||
|
||||
The modules do not know how to present the information though. This is
|
||||
instead done by particles. And the user, you, decides which particles (and
|
||||
thus how to present the data) to use.
|
||||
|
||||
Furthermore, each particle can have a decoration - a background color or a
|
||||
graphical underline, for example.
|
||||
|
||||
There is no support for images or icons. use an icon font (e.g. Font
|
||||
Awesome, or Material Icons) if you want a graphical representation.
|
||||
|
||||
There are a number of modules and particles builtin. More can be added as
|
||||
plugins. You can even write your own!
|
||||
|
||||
To summarize: a bar displays information provided by modules, using
|
||||
particles and decorations. How is configured by you.
|
||||
'';
|
||||
license = licenses.mit;
|
||||
maintainers = with maintainers; [ AndersonTorres ];
|
||||
platforms = with platforms; unix;
|
||||
};
|
||||
}
|
|
@ -23849,6 +23849,8 @@ in
|
|||
i3GapsSupport = false;
|
||||
};
|
||||
|
||||
yambar = callPackage ../applications/misc/yambar { };
|
||||
|
||||
polyphone = libsForQt514.callPackage ../applications/audio/polyphone { };
|
||||
|
||||
portfolio = callPackage ../applications/office/portfolio {
|
||||
|
|
Loading…
Reference in a new issue