| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Build mandoc from cvs and apply a patch which adds an exception for
the checks does makewhatis(8): with this the realpaths of man pages to
be indexed may be symlinks referring to files outside of the root man
directory if they are located in /nix/store.
This allows indexing /run/current-system/sw/share/man using mandoc's
makewhatis(8).
Since fetchcvs is currently broken in nixos-unstable we vendor in the
fixed variant from nixpkgs master until the channel has advanced.
|
|
|
|
|
|
| |
Couldn't figure out how to pass a string from a command which contains
spaces from a variable to a command without the string getting split
into two arguments, so nested shell it is.
|
|
|
|
|
|
|
|
| |
Even if GIT_PAGER is set to less alone, git diff will pass extra options
to less, so we have to explicictly set the LESS="..." environment
variable to change this behavior. Specifically we don't want -F which
prevents less from entering alternate mode which enables alternate
scrolling in foot.
|
|
|
|
| |
vuizvui currently ships no programs.sqlite
|
| |
|
|
|
|
|
|
|
|
| |
After some experimentation and looking at the NixOS' hardware repo, this
configuration seems to work quite well. There are no major issues to
worry about for now.
This is also the first machine where `fwupd` is available and working.
|
| |
|
|
|
|
|
| |
This fixes the build of pkgs.profpatsch.watch-server, it was likely only
forgotten to update the revision in vuizvui.
|
| |
|
|
|
|
| |
machines/sternenseemann/wolfgang: refactor using new sway module
|
| |
|
|
|
|
| |
machines/sternenseemann: add TODO list
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
| |
sterni's personal texlive.combine { ... }
|
|
|
|
| |
sterni's patched pass with passmenu
|
| |
|
| |
|
| |
|
|
|
|
| |
pkgs/sternenseemann/emoji-generic: init at unstable-2020-11-22
|
|
|
|
|
| |
This machine is no longer active and probably would have to be redone
completely should it be reactivated.
|
|
|
|
|
| |
This machine has been replaced and now runs Windows for playing
minecraft mostly.
|
|
|
|
|
| |
This machine is no longer active and not really feasibly usable with
NixOS since i686 support was dropped.
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
We originally needed it here to deploy it on the machine, but it’s set
up manually via the gitit repo default.nix for the time being.
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Upstream is deprecating `stdenv.lib`, so let’s do the same.
|
|
|
|
| |
Small script to deploy my machines.
|
|
|
|
|
|
|
|
|
|
|
| |
skarnet thought it would be wise to completely change the skalibs
exec function interface without any backwards compat, so here we are.
Have to reverse the code a bit, because `xmexec0` is a recursive
`#define` pointing to `xmexec0_af`.
`record-get` gets a rust treatment, it doesn’t really need the C
interface just to exec into prog.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Shiny new machine needs NixOS love. <3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 7b8164be35c9d82d6e7389a407150a9128f7fb0c.
From the upstream changelog:
> This is an important bugfix release that should resolve several
> outstanding issues and concerns. Since 1.10.0 was released was engaged
> in a lot of discussions and realized that compatibility is more
> important than we first thought. So we're rolling back some breaking
> changes and revise some parts of our roadmap. We will strive to remain
> compatible with other password store implementations - but remember
> this is a goal, not a promise. This means we'll continue using
> compatible secrets formats as well as GPG and Git.
As mentioned in the original commit, I'm still not entirely convinced
that my use case has a future with gopass, their decision to roll back
some of the breaking changes at least makes it possible for me to
upgrade to the latest upstream version without the fear of being locked
in into some gopass-specific format.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
| |
I've been experiencing some nasty tearing and flickering lately. This
was a good opportunity to also change some settings.
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
These are not needed nearly as much as they once did.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Injecting pre/post start scripts into services called
"btrfs-scrub-.service.service" isn't going to do a whole lot if the
actual service name is called "btrfs-scrub-.service".
During the last scrub I was wondering why caching got slow afterwards
and found out that the caching devices were filled with lots of
irrelevant data from the scrub. This led me to inspect what went wrong
and when checking the properties of the scrub service unit, I found out
that it never worked in the first place for the reason meantioned in the
first paragraph.
Actually using the right unit name helps a lot here, so onwards to the
next scrub in February :-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
Dumb wrapper around `nix-instantiate` for something I often need.
|
| |
|
|
|
|
|
|
|
|
|
| |
Small tool which takes a block of nix options that should produce a
script to run, and then calls the script with the rest of argv
e nix-run { -A foobar } a b c
calls `nix-build -A foobar && ./result a b c`.
|
|
|
|
|
|
|
|
|
|
| |
This is a working PoC of specifying module configs as toml
configuration with simple to understand semantics.
Both the option definitions and the actual config values can be
specified via the toml DSL.
This is extremely happy-path for now, so errors are gonna be horrible.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This has been laying around since a few weeks but instead of just using
a simple shell script wrapper (which I had in the first place), I
decided to directly patch the binary during rC3.
The main reason why I went this route was because in the long run we
want to have a generic implementation we can use to patch all sorts of
games, similar to what we have with monogame-patcher.
So the way the *current* patcher roughly works is by allocating an area
called "compost", which is then used as some kind of abstraction for
allocating code and data to be used for the references/logic that we
need to patch.
The latter involves patching XDG_DATA_HOME into the game and changing
the "/usr/share/factorio" path to use the ones within the store path
($out/share/factorio). Fortunately, Factorio already assumes that
everything within /usr/share/factorio (or our path for that matter) is
read-only, so we don't need to add extra code/conditions specifically to
handle that.
Patching both cases is made possible by patching a third location
(get_executable_name), which tries to get the current executable path
via several methods (using /proc/self/exe, running "ps", ...) at
runtime, which in our case is really unnecessary and a perfect
opportunity to replace the function logic by the hardcoded path and
using the rest of the function for our compost area.
While patching might sound straigtforward, I actually introduced two
little (but hard to debug) bugs, where I'm very grateful to all those
folks (you know who you are) at rC3 who were actually following along
and provided helpful input.
In the long term, the goal is to rewrite the patcher with more elaborate
type information (eg. right now function/opcode information is raw JSON)
and generalise it enough that we can use it to get rid of a few other
wrappers.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since the goal of using `e` with argv is interactive execution of
block-style commands from the command line, the use of { and } for
blocks is sub-optimal, since bash (and ostensibly also fish) interpret
them as metacharacters and assign some semantics.
[ and ] on the other hand are not taken (apart from the `[`
executable, which is only relevant in command position and can always
be replaced by the `test` command). So we translate a stand-alone "["
argument to "{" and the same for "]"/"}", giving us a transparent
block syntax.
|