about summary refs log tree commit diff
path: root/modules
Commit message (Collapse)AuthorAgeFilesLines
* modules/user/sternenseemann/sway: fix startup by enabling openglsternenseemann2021-02-111-0/+2
| | | | | | | Due to a previous oversight hardware.opengl.enable = true; wasn't set anymore (previously it was by programs.sway which has been replaced). Thus sway couldn't load the necessary OpenGL driver's anymore after a reboot.
* Revert "modules/user/sternenseemann/sway: fix startup by enabling opengl"sternenseemann2021-02-111-2/+0
| | | | | | This reverts commit 5bd756eaf27882820cb59e0ecf9c305f08b3b3e3. Committed more than I meant to.
* modules/user/aszlig/managed: disable flashsternenseemann2021-02-111-1/+0
| | | | | | | | | | nixpkgs has removed flash support in chromium without replacement in d55603f11d36ae38ca76dec8d95bc55d2115f104 following the removal in upstream chromium M88, so I'm disabling it completely in vuizvui.user.aszlig.profiles.managed to fix the evaluation of shiki and brawndo. cc @aszlig
* modules/user/sternenseemann/sway: fix startup by enabling openglsternenseemann2021-02-111-0/+2
| | | | | | sway needs opengl driver's to be enabled and loadable in order to start. I previously didn't notice this oversight as I still had them loaded and did not reboot after the rebuild.
* profiles/packages: Add nixfmtdevhell2021-02-091-0/+1
|
* modules/user/sternenseemann: add mandoc modulesternenseemann2021-02-092-0/+113
| | | | | | | | | | This module implements a drop-in replacement for documentation.man which finally lets me get rid of pkgs.man-db. This is still to be considered experimental as the required patch hasn't landed in upstream mandoc yet. Should that happen, I'll try to contribute this module back to nixpkgs. A more detailed description on the module and mandoc on NixOS can be found at the top of modules/user/sternenseemann/documentation/mandoc.nix
* profiles/packages: Add and remove some toolsdevhell2021-02-081-5/+5
|
* modules/user/sternenseemann: add sway service modulesternenseemann2021-02-072-0/+318
| | | | machines/sternenseemann/wolfgang: refactor using new sway module
* modules/programs/foot: initsternenseemann2021-02-072-0/+205
| | | | | | | Module for the foot (wayland) terminal emulator. Approach for this module is to take advantage of toINI and freeform module types to allow users to freely set any option while still offering some higher level representations for fields where plain strings would be inconvenient.
* profiles/managed: Fix kdeApplications eval erroraszlig2021-02-051-10/+10
| | | | | | | | | The kdeApplications attribute got removed from the top-level a while ago, so the machines using the "managed" profile no longer evaluate. Instead, the plasma5Packages exposes the same set of packages. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/base: Disable Beets "Alternatives" pluginaszlig2021-02-051-3/+0
| | | | | | | | | | I no longer use this plugin and since evaluation currently is broken upstream (blocked by [1]), let's make sure that at least the rest of Vuizvui continues to evaluate. [1]: https://github.com/NixOS/nixpkgs/pull/109679 Signed-off-by: aszlig <aszlig@nix.build>
* profiles/services: Rework picomdevhell2021-01-101-0/+5
| | | | | I've been experiencing some nasty tearing and flickering lately. This was a good opportunity to also change some settings.
* profiles/{packages,services}: polybar -> i3status-rustdevhell2021-01-102-1/+1
| | | | | | I'm a bit tired of polybar and am very interested in i3status-rust, however, the latter isn't a perfect replacement yet, so I'm going to continue experimenting with it.
* profiles/packages: Clear some unneeded packagesdevhell2021-01-071-5/+0
| | | | These are not needed nearly as much as they once did.
* modules/aszlig: Remove Taskwarrior moduleaszlig2020-12-234-86/+0
| | | | | | | | I no longer use Taskwarrior and since my config.patch fails to apply in the most recent release, I think it's time to finally remove it from my workstation profile. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/base: Add helper for showing last Nix logaszlig2020-12-101-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | This is a common pattern I encounter on a daily basis, which involves copy & pasting the store path of a failed build to "nix log". Now the same is just a matter of running "nlast" and we get rid of the useless copy & paste. The way we do this does have a small goof: Using mtime (or really any time, other than atime, which commonly is disabled) is not going to work if we *repeat* an older Nix build, since this will only change the log file but the prefix directory will be unchanged. Since addressing this goof would most likely result in iterating through *all* log files, I'm not doing it since I think it doesn't occur very often in practice. If I happen to be wrong on that, we could still go for the heavyweight solution. Also, I went for implementing this in Python instead of a shell script, because the latter would not only be less readable but also way slower since we need to either fork out for every stat command or use ls and head to figure out the newest file. Signed-off-by: aszlig <aszlig@nix.build>
* devhell/vim: Change vim from module to packagedevhell2020-12-041-1/+1
| | | | Recommended by aszlig to switch from module to package.
* workstation/packages: Remove NixOpsaszlig2020-12-041-1/+0
| | | | | | | | | | | | | | | | Since the "cryptography" Python library is marked as insecure I'd have several options here: Add an excemption for the library, switch to NixOps 2.0 or entirely remove it. I chose to do the latter, since on all of my deployments I currently use a heavily patched NixOps version which is somewhat of a mix between 1.5 and 2.0 and the version used here in the workstation profile is unused since ages anyway. In case I really need to use nixops on any of my workstations again, I could still resort to "nix run". Signed-off-by: aszlig <aszlig@nix.build>
* profiles/packages: Remove vim_configurabledevhell2020-12-041-1/+0
| | | | | This led to an issue where `vim` and `vimdiff` were launched from two different derivations.
* profile/base: Remove more fontsdevhell2020-11-301-2/+0
| | | | Don't need these either really.
* profiles/base: Add Nerd Font, remove othersdevhell2020-11-301-12/+1
| | | | | Nerd Fonts looks interesting and should replace most of the ones I already use.
* programs/vim: Remove dracula, add vimtexdevhell2020-11-261-4/+9
| | | | | | | I just like `tender` colorscheme too much, and also `dracula` didn't work very well. Although most of my LaTeX work is done on Overleaf, sometimes I do need some good local LaTeX support in vim, so let's give `vimtex` a chance.
* profiles/base: Rework ZSH configurationdevhell2020-11-231-2/+36
| | | | | | | | | | I've been trying to get most of my environment directly configured via my NixOS configuration rather than rely on my dotfiles repository, if the program/configuration is well supported in NixOS. Just like Vim, here too I'm relying more on NixOS' ZSH options, which truly eliminates dependencies on external repositories or dotfile setups.
* profiles/packages: Add gh clidevhell2020-11-181-0/+1
| | | | Might be less annoying that having to do things via the browser.
* profiles/packages: Remove termitedevhell2020-11-161-1/+0
| | | | I'm very happy with `alacritty`, so I'm dropping `termite`.
* profiles/packages: Add vividdevhell2020-11-141-0/+1
|
* programs/vim: Rework vimdevhell2020-11-121-14/+23
| | | | Now it's pretty much the way I want it.
* modules: Rename enableFontDir to fontDir.enableaszlig2020-11-101-1/+1
| | | | | | | | | The option has been renamed since a while[1] ago, so to get rid of annoying warnings, let's actually switch to the new option name. [1]: https://github.com/NixOS/nixpkgs/commit/c99bd9bedf7291390c28eddb31f Signed-off-by: aszlig <aszlig@nix.build>
* programs/vim: Remove sensible and enable settingsdevhell2020-11-091-17/+18
| | | | | The `sensible` plugin doesn't work for me. I think setting things manually is probably better for now.
* profiles/packages: Remove taskelldevhell2020-11-091-1/+0
| | | | It's marked as broken and I've been using `smos` more lately anyway.
* programs/vim: Add sleuth plugindevhell2020-11-061-0/+1
| | | | Fully automatic indentation, why not.
* {machines,modules}: Enable Podman everywheredevhell2020-11-062-0/+3
| | | | | I'm finding myself use containers more and more these days, primarily for testing stuff, so it's useful to have the tools installed.
* modules/vim: Add cursorlinedevhell2020-11-051-0/+1
|
* profiles/packages: Remove xscreensaverdevhell2020-11-051-1/+0
| | | | Forgot I had this still in here.
* modules/programs: Fix Vimdevhell2020-11-051-55/+70
| | | | | | | This config works now. Huge thanks to aszlig for helping! This is only a bare-bones configurations. There are some parts of SpaceVim I really enjoy, so over time I'll try to get my Vim configuration to emulate those parts.
* modules/programs: Add vimdevhell2020-11-032-0/+58
| | | | | | This is in preparation of me leaving SpaceVim behind and not having to rely on external sources for certain programs, such as Vim, when installing a new machine.
* profile/packages: Replace scrot with maimdevhell2020-10-301-1/+1
| | | | | | | I'm not sure when this started, but `scrot -s` introduces artefacts in the screenshot because the selection border is captured with the screenshot which is pretty annoying. It looks like `maim` doesn't have this issue.
* core/tests: Remove runInMachineaszlig2020-10-221-3/+0
| | | | | | | | | | | | | | | | | The test is not essential for running any real NixOS machines and the tests just checks whether the runInMachine function for building derivations inside a VM works. I was very much reluctant to just remove this test before I actually fixed the issue upstream because this would mean that it's highly likely that I'm never going to do it. However, since all the channels on our side are currently blocking on this test, which isn't relevant either, I'm going to risk possibly never fixing runInMachine upstream since I'd have removed that test anyway for the aforementioned reason. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/packages: Add 'so'devhell2020-10-201-0/+1
| | | | This is incredibly useful if you don't want to leave the terminal.
* profiles/packages: Add bottom, remove othersdevhell2020-10-201-6/+1
|
* profiles/packages: Add batdevhell2020-10-151-0/+1
| | | | Neat. Like cat, just better in certain circumstances.
* Revert "Revert "profiles/base: Allow mpd to access pulseaudio""devhell2020-10-141-0/+1
| | | | | | | Well, that was a bit too hasty, I forgot that MPD runs as its own user and therefore can't talk to pulseaudio if this isn't set. This reverts commit dc4882e92f84c157d682b860365644ffd1f5c0d6.
* profiles/packages: Add smosdevhell2020-10-131-0/+1
| | | | | This seems like an immensely useful tool in conjunction with `taskwarrior`.
* core/tests: Remove all tests from the "tested" jobaszlig2020-10-041-248/+5
| | | | | | | | | | | | | | | | | | | | The upstream Hydra channels are based on the "tested" job in release-combined.nix, which already contain a bunch of tests that must succeed for the channel to advance. Since evaluation time has skyrocketed for us within the last few months, we now even don't get *any* evaluation since a while since we hit a timeout of 10 hours. I have no idea which changes resulted in this spike of evaluation time but right now I'm too busy with other things to do a proper investigation. To hopefully mitigate this, I decided to base our vuizvui jobset on the "nixos-unstable" channel and we now only run *additional* tests not already tested by the upstream channel. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/packages: Add dufdevhell2020-10-011-0/+1
| | | | | Reat that muesli made this lovely little tool, so naturally had to add it.
* modules/profpatsch/services/dunst: display icons by defaultProfpatsch2020-09-211-0/+2
|
* modules/profpatsch/services: add dunst user serviceProfpatsch2020-09-212-0/+118
|
* Use attribute sets for boot.initrd.luks.devicesaszlig2020-09-141-1/+1
| | | | | | | | | | | | | | | | | | | | This was one of the places where types.loaOf was still in place and it got removed a while[1] ago and this in turn causes evaluation to fail for quite a few machines: The option value `boot.initrd.luks.devices' in `...' is not of type `attribute set of submodules'. I've not only changed all the machines to use attribute sets but also fixed the check in core/tests.nix, because comparing against a list when the actual type is an attribute set will result in all the LUKS tests to be part of *all* channels, no matter whether you're actually using LUKS. [1]: https://github.com/NixOS/nixpkgs/commit/20d491a317d9956ddca80913f07 Signed-off-by: aszlig <aszlig@nix.build> Cc: @Profpatsch Cc: @sternenseemann
* devhell/packages: Remove gstreamer packageaszlig2020-09-141-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The package attributes for GSstreamer 0.x were dropped[1] a while ago, so evaluating the packages no longer succeeds and instead we get an error like this on Hydra: error: undefined variable 'gstreamer' at .../profiles/packages.nix:129:7 Initially I was tempted to change this to use pkgs.gst_all_1.gstreamer, but looking at the differences between the old pkgs.gstreamer, the new package only contains the relevant libraries while the old one contains a few binaries, namely gst-feedback, gst-inspect, gst-launch, gst-typefind, gst-xmlinspect, gst-xmllaunch and all of them again with a "-0.10" suffix. All of these tools are development tools and should not be used in real applications, for example from the manual[2] on gst-launch-1.0: > Please note that gst-launch-1.0 is primarily a debugging tool. You > should not build applications on top of it. For applications, use the > gst_parse_launch() function of the GStreamer API as an easy way to > construct pipelines from pipeline descriptions. While environment.systemPackages does link other directories than just $out/bin, the primary reason why you'd want to put something in there is to make it available in the system's PATH. When asking @devhell about this he didn't remember the exact reason why he put gstreamer in systemPackages, so I can only *assume* it was because of tools like gst-launch, which unfortunately even I can remember seeing recommended (instead of eg. ffmpeg) in some dark corners of the web. So if this would be really about gst-launch, we would need to put in pkgs.gst_all_1.gstreamer.dev into systemPackages, since the development tools are now where they belong. Given that @devhell doesn't know the reason anymore and *also* told me to remove it *and* it's also just a development tool which is not supposed to be used in production, I'm hereby removing the package. Should there really be applications which rely on this, they should hopefully break after this change so they can be fixed to not rely on these development tools. [1]: https://github.com/NixOS/nixpkgs/commit/4a4e642abaaa026b55f42248a7b [2]: https://gstreamer.freedesktop.org/documentation/tools/gst-launch.html Signed-off-by: aszlig <aszlig@nix.build> Cc: @devhell
* modules/gnupg: Use getLib to get systemd libraryaszlig2020-09-081-1/+1
| | | | | | | | | | | | | A recent change[1] has removed the lib output from the systemd package, so our GnuPG agent wrapper no longer compiles. Using getLib falls back to the "out" output if the "lib" output is unavailable and should be backwards- and forwards-compatible (in case the "lib" output is added back someday). [1]: https://github.com/NixOS/nixpkgs/commit/b68bddfbda2092c5fde2c4cece2 Signed-off-by: aszlig <aszlig@nix.build>
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-30 14:46:15 +0000