| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Nope, never mind, maple is still not building, therefore vim-clap can't
build.
This reverts commit 4d4f07ef82d8a19587cc450b6d0a198e16acb48f.
|
|
|
|
| |
Apparently this builds again according to `hydra-check`.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The patch file was relative to the rustfmt crate within the rustc source
tree, so I added "-d src/tools/rustfmt" as patchFlags to apply the patch
against that subdirectory.
Unfortunately, patchFlags also applies to other patches as well and I
didn't account for that. With current rustfmt from rustc 1.59.0 we have
a patch in nixpkgs, which now fails to apply because of this:
applying patch /nix/store/...-rustfmt-fix-self-tests.patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/src/tools/rustfmt/src/ignore_path.rs
|+++ b/src/tools/rustfmt/src/ignore_path.rs
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
To fix this, I changed the paths in config.patch to be relative to the
rustc tree rather than just the rustfmt crate, so the patch should now
apply regardless of whether there are other patches.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
*sigh*
|
|
|
|
|
|
| |
* plumb/plumber for mouse 3
* rc for mouse 2
* win for terminal feature
|
| |
|
|
|
|
|
|
|
| |
The patch no longer applies because some of the imports got changed in
the context of the diff.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The version from 2021 certainly is way too old for my desire to crave
new bugs, so let's update it for no particular reason other than gut
feeling.
Oh, well and of course I saw a bunch of OMEMO plugin fixes, so maybe if
you search hard enough you'll find compelling reasons... :-D
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
nix_2_3 is an alias for nixVersions.nix_2_3 upstream now and the test
infrastructure from nixpkgs seems to default to allowAliases = false;
when evaluating (which is actually quite concerning for downstream
usage).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
depot is a nix-based monorepo which contains some great nix utilities
like yants (a nix type system), runTestsuite, mergePatch and so on, a
few interesting pure nix builders like buildLisp and buildGo and a few
packages maintained by @Profpatsch and myself.
This change exposes tvl completely as pkgs.tvl, but prevents hydra from
building it using dontRecurseIntoAttrs as depot pins its own version of
nixpkgs which is not easily overrideable, contains some expensive to
build system configurations we are not interested in and even some
notoriously indeterministic packages.
Additionally it is possible to override pkgs.tvl to use a different or
local version of depot:
pkgs.tvl.override { tvlSrc = /home/lukas/src/depot; }
To keep with @Profpatsch's previous solution, we pass in vuizvui's
nixpkgs version to depot via nixpkgsBisectPath which may break packages
in depot occasionally if nixpkgs causes breakage in TVL and depot isn't
updated accordingly.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Patch plan9port most notably including a patch that fixes the
interpretation of X11 key events. This resolves the problem that using
the shift key of the neo layout would cause acme to start interpreting
left mouse button as right mouse button.
* Add a wrapper derivation that puts acme and all executables it
absolutely requires in PATH. The full Plan 9 userland can still be
accessed via the 9 executable, but this allows executing just acme and
access e.g. the GNU coreutils from inside of it — in case you do want
to use cat -v.
machines/sternenseemann/wolfgang: install acme
|
| |
|
| |
|
|
|
|
|
| |
There are some issues with building `mkdx`, but I'm also not really
happy with the way it does markdown.
|
| |
|
|
|
|
|
|
| |
pkgs.vuizvui is made available via an overlay that only affects a system
configuration with the base vuizvui module included. When importing the
pkgs tree directly, normal rules apply.
|
|
|
|
|
|
|
| |
This is the alacritty wrapper that is added from `~/bin`.
This is a bit badly set up atm, but might change once I move things
together into one repo.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It’s hard-coded as the default case in our script already, this was
breaking that functionality.
|
|
|
|
|
|
|
|
|
| |
The way store paths are queried has changed significantly in Nix 2.4, so
we need to completely refactor nix-query.cc. However, I currently have a
lot of other things to do and the store protocol is compatible so let's
pin Nix to version 2.3 for the sandbox implementation for now.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since I do have a lot of projects where I use rustfmt, it gets pretty
tedious to manually run "cargo fmt". Using g:rustfmt_autosave should
make this less tedious but it might annoy me in the future, let's see.
In addition to setting rustfmt I also added a default path for rustc,
which is used whenever there is no rustc in path. This is because I
usually switch between several projects which use different Rust
versions and this way it will use the rustc version that is in PATH
during "nix develop".
For the rustfmt part I also added a small default configuration which
represents my opinion on how I think Rust code should be formatted. The
file is used whenever a project doesn't have a "rustfmt.toml" or
".rustfmt.toml".
Unfortunately, RustFmt is broken in Vim right now[1], so I'm using the
upstream project until the issue has been resolved.
[1]: https://github.com/rust-lang/rust.vim/issues/446
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
I'm using org mode for these kinds of things now.
|
|
|
|
|
|
| |
If you want to use multiple binaries (e.g. via `pkgs.symlinkJoin`),
this will work via PATH instead of magically tranforming the first
argument instead.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Takes an additional argument and looks that argument up in the
respective nix build result directory bin dir.
Also add some documentation.
|
| |
|
|
|
|
|
| |
It’s always a mistake to forget a block here, so this will give a
better error message.
|
|
|
|
| |
It’s not worth the indirection.
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Delete patched mandoc derivation and documentation.mandoc module from
the tree, both have an equivalent upstream now.
* Activate upstreamed documentation.man.mandoc module in my machines.
|
| |
|
|
|
|
| |
forgot to commit this the first time around
|
| |
|
| |
|
|
|
|
| |
This should do the trick.
|
|
|
|
| |
Argh
|
| |
|
|
|
|
|
|
|
|
| |
The hydra still doesn’t like the import:
error: "\u001b[31;1merror:\u001b[0m\u001b[34;1m --- RestrictedPathError --- hydra-eval-jobs\u001b[0m\naccess to path '\u001b[33;1m/nix/store/b6ba70kcrvnxq165h791l71wvmdj2qy1-prepare-tvl\u001b[0m' is forbidden in restricted mode"
So let’s try this.
|
| |
|
| |
|
|
|
|
|
| |
We don’t want any builtins.fetchgit stuff from random domains,
hopefully this will fix the current eval error.
|
|
|
|
| |
All relevant patches have made it into a release finally!
|