JakeHillion/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
4f07e7f326
nixpkgs/nixos/tests/yabar.nix

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

34 lines
666 B
Nix
Raw Normal View History

nixos/yabar: port test to python
2019-11-06 06:54:16 +00:00
import ./make-test-python.nix ({ pkgs, lib, ... }:
yabar: add module To make the configuration of `yabar` more pleasant and easier to validate, a NixOS module will be quite helpful. An example config could look like this: ``` { programs.yabar = { enable = true; bars.top.indicators.exec = "YA_DATE"; }; } ``` The module adds a user-controlled systemd service which runs `yabar` after starting up X.
2017-12-12 00:14:00 +00:00
with lib;
{
name = "yabar";
treewide: simplify pkgs.stdenv.lib -> pkgs.lib The library does not depend on stdenv, that `stdenv` exposes `lib` is an artifact of the ancient origins of nixpkgs.
2021-01-10 19:08:30 +00:00
meta = with pkgs.lib.maintainers; {
treewide: remove ma27 from the maintainer-list of a few packages These are all packages that I stopped using and hence just create noise in my inbox for each change affecting them and let's face it, while I still enjoy contributing to nixpkgs, it doesn't really make sense to be listed there if I can't do much anyways. Each of these packages can be taken over by someone or removed if people think that's reasonable. Of course, if other maintainers face issues, I can answer some questions if needed & possible.
2021-08-27 21:09:49 +01:00
maintainers = [ ];
yabar: add module To make the configuration of `yabar` more pleasant and easier to validate, a NixOS module will be quite helpful. An example config could look like this: ``` { programs.yabar = { enable = true; bars.top.indicators.exec = "YA_DATE"; }; } ``` The module adds a user-controlled systemd service which runs `yabar` after starting up X.
2017-12-12 00:14:00 +00:00
};
treewide: machine -> nodes.machine
2022-03-20 23:15:30 +00:00
nodes.machine = {
yabar: add module To make the configuration of `yabar` more pleasant and easier to validate, a NixOS module will be quite helpful. An example config could look like this: ``` { programs.yabar = { enable = true; bars.top.indicators.exec = "YA_DATE"; }; } ``` The module adds a user-controlled systemd service which runs `yabar` after starting up X.
2017-12-12 00:14:00 +00:00
imports = [ ./common/x11.nix ./common/user-account.nix ];
nixos/display-managers/auto: remove This module allows root autoLogin, so we would break that for users, but they shouldn't be using it anyways. This gives the impression like auto is some special display manager, when it's just lightdm and special pam rules to allow root autoLogin. It was created for NixOS's testing so I believe this is where it belongs.
2020-01-26 22:41:19 +00:00
test-support.displayManager.auto.user = "bob";
yabar: add module To make the configuration of `yabar` more pleasant and easier to validate, a NixOS module will be quite helpful. An example config could look like this: ``` { programs.yabar = { enable = true; bars.top.indicators.exec = "YA_DATE"; }; } ``` The module adds a user-controlled systemd service which runs `yabar` after starting up X.
2017-12-12 00:14:00 +00:00
programs.yabar.enable = true;
nixos/yabar: fix module & test (#46954) The `pkgs.yabar` package is relatively old (2016-04) and contains several issues fixed on master. `yabar-unstable` containsa recent master build with several fixes and a lot of new features (I use `yabar-unstable` for some time now and had no issues with it). In the upstream bugtracker some bugs could be fixed on ArchLinux by simply installing `yabar-git` (an AUR package which builds a recent master). To stabilize the module, the option `programs.yabar.package` now defaults to `pkgs.yabar-unstable` and yields a warning with several linked issues that are known on `pkgs.yabar`. The test has been refactored as well to ensure that `yabar` actually starts (and avoid non-deterministic random success) and takes a screenshot of a very minimalistic configuration on IceWM. Fixes #46899
2018-09-20 11:47:46 +01:00
programs.yabar.bars = {
top.indicators.date.exec = "YABAR_DATE";
};
yabar: add module To make the configuration of `yabar` more pleasant and easier to validate, a NixOS module will be quite helpful. An example config could look like this: ``` { programs.yabar = { enable = true; bars.top.indicators.exec = "YA_DATE"; }; } ``` The module adds a user-controlled systemd service which runs `yabar` after starting up X.
2017-12-12 00:14:00 +00:00
};
testScript = ''
nixos/yabar: port test to python
2019-11-06 06:54:16 +00:00
machine.start()
machine.wait_for_x()
yabar: add module To make the configuration of `yabar` more pleasant and easier to validate, a NixOS module will be quite helpful. An example config could look like this: ``` { programs.yabar = { enable = true; bars.top.indicators.exec = "YA_DATE"; }; } ``` The module adds a user-controlled systemd service which runs `yabar` after starting up X.
2017-12-12 00:14:00 +00:00
nixos/yabar: fix module & test (#46954) The `pkgs.yabar` package is relatively old (2016-04) and contains several issues fixed on master. `yabar-unstable` containsa recent master build with several fixes and a lot of new features (I use `yabar-unstable` for some time now and had no issues with it). In the upstream bugtracker some bugs could be fixed on ArchLinux by simply installing `yabar-git` (an AUR package which builds a recent master). To stabilize the module, the option `programs.yabar.package` now defaults to `pkgs.yabar-unstable` and yields a warning with several linked issues that are known on `pkgs.yabar`. The test has been refactored as well to ensure that `yabar` actually starts (and avoid non-deterministic random success) and takes a screenshot of a very minimalistic configuration on IceWM. Fixes #46899
2018-09-20 11:47:46 +01:00
# confirm proper startup
nixos/yabar: port test to python
2019-11-06 06:54:16 +00:00
machine.wait_for_unit("yabar.service", "bob")
machine.sleep(10)
machine.wait_for_unit("yabar.service", "bob")
nixos/yabar: fix module & test (#46954) The `pkgs.yabar` package is relatively old (2016-04) and contains several issues fixed on master. `yabar-unstable` containsa recent master build with several fixes and a lot of new features (I use `yabar-unstable` for some time now and had no issues with it). In the upstream bugtracker some bugs could be fixed on ArchLinux by simply installing `yabar-git` (an AUR package which builds a recent master). To stabilize the module, the option `programs.yabar.package` now defaults to `pkgs.yabar-unstable` and yields a warning with several linked issues that are known on `pkgs.yabar`. The test has been refactored as well to ensure that `yabar` actually starts (and avoid non-deterministic random success) and takes a screenshot of a very minimalistic configuration on IceWM. Fixes #46899
2018-09-20 11:47:46 +01:00
nixos/yabar: port test to python
2019-11-06 06:54:16 +00:00
machine.screenshot("top_bar")
yabar: add module To make the configuration of `yabar` more pleasant and easier to validate, a NixOS module will be quite helpful. An example config could look like this: ``` { programs.yabar = { enable = true; bars.top.indicators.exec = "YA_DATE"; }; } ``` The module adds a user-controlled systemd service which runs `yabar` after starting up X.
2017-12-12 00:14:00 +00:00
'';
})
Reference in New Issue Copy Permalink