| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Somebody wanted a very old MLP file I posted years ago, restores the
public URL.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This reverts commit e08ff60d61bb18dcd14a47f2ee6dec66ad8cbd91.
The CVE fixes have long been upstreamed.
|
| | |
|
| |
|
|
| |
cc @Profpatsch @aszlig
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The "vim_configurable" derivation has had a long history in nixpkgs back
then when there was no RFC process and where people still were figuring
out better ways on how to configure compile-time flags.
One of those was a composableDerivation function, which was used for
"vim_configurable" and mapped attribute sets to autoconf-flags, so that
for example if there was a "--enable-foo" flag you could just use
something like:
vim_configurable.merge { cfg.fooSupport = true; }
You'd then get a Vim with "--enable-foo" passed to configureFlags.
However, the composableDerivation feature was too complicated and was
ultimately removed at some point. While it does allow for things such as
introducing new "edf" (stands for Enable Disable Feature and maps the
autoconf flags mentioned above to attribute sets) flags, the complexity
that comes with that system is way too large than using something like
eg.:
vim-full.overrideAttrs (drv: {
configureFlags = (drv.configureFlags or []) ++ [ "--enable-foo" ];
})
While this looks more verbose than the above, one can easily follow
what's happening, whereas if you'd need to add and enable a new "edf"
flag, you'd do something like this:
vim_configurable.merge {
flags = composableDerivation.edf { name = "foo"; };
cfg.fooSupport = true;
}
I admit that this does look a little nicer, but even I'm not sure
whether it's worth adding so much complexity since in practice I rarely
came across a sitation where something like the above would be really
beneficial.
So back then when "vim_configurable" was introduced[1], it was used as
an alternative to the main vim derivation but using composableDerivation
instead.
Nowadays however, vim_configurable no longer uses composableDerivation
and the rename also doesn't change any features, so I think it's safe to
rename vim_configurable to vim-full in Vuizvui.
[1]: https://github.com/NixOS/nixpkgs/commit/9a4e9e7a3b4014bb3c9f678ec22d254b85c4c98a
[2]: https://github.com/NixOS/nixpkgs/commit/4e5ebcc3ed1de9c5c2001c7d5829f4566e0bde3f
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
Cc: @devhell
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
CVE patch is out already, but let’s wait until upstream has all the
patches.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Comment out a lot of the old stuff that I might not want to re-enable
later. And get rid of the pre-tailscale wireguard desaster.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most of the options in nix.conf are now exposed as a submodule with a
freeform type and since that change[1] got introduced, we get a bunch of
warnings during machine evaluation:
trace: warning: The option `nix.useSandbox' defined in `...' has been renamed to `nix.settings.sandbox'.
trace: warning: The option `nix.maxJobs' defined in `...' has been renamed to `nix.settings.max-jobs'.
trace: warning: The option `nix.buildCores' defined in `...' has been renamed to `nix.settings.cores'.
To shut them up, I went through all machines and modules and renamed the
remaining options that were not renamed back then when @devhell did some
renames in a0297bf921399c3243dcca99626d8697f0735abe.
This was done by looking through the output of:
$ git grep -A 10 '\<nix\(\.\| *=\)' machines modules
After that I tested the contents of the nix.conf of all the machines
against the changes this commit introduced via the following command:
$ nix-build --no-out-link -E '
with import <nixpkgs/lib>;
map (m: m.eval.config.environment.etc."nix/nix.conf".source)
(collect (m: m ? eval) (import ./machines))
'
I've sorted the resulting nix.conf files and diffed on that result and
the only difference that showed up was the following:
allowed-users = *
-auto-optimise-store = false
auto-optimise-store = true
builders-use-substitutes = true
cores = 0
This is because the previous way to generate the config was by
concatenating strings whereas the new way works on an attribute set, so
we get deduplication by design.
[1]: https://github.com/NixOS/nixpkgs/pull/139075
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @devhell
Cc: @Profpatsch
Cc: @sternenseemann
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
No! bad subvolume! bad!
|
| |
|
|
|
|
| |
I had them copied from the wrong module, of course this can’t work.
Since the kernel config & boot loader config is now in thinkpad, this
might just work (famous last words).
|
| |
|
|
|
| |
Not sure about the boot loader config, but I guess it’s okay for now,
since it doesn’t diverge anyway.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
I use all of that on a regular basis.
Earlyoom makes sense for any kind of machine without swap, which is
all of my machines.
|
| |
|
|
|
| |
I want to have a thinkpad-based server, which will need the
thinkpad-specific stuff but none of the workstation stuff.
|
| |
|
|
|
|
|
|
| |
Not updating the microcode on thinkpads is kind of a death sentence
for some kernel updates, so let’s do it by default.
In case somebody uses it for an AMD thinkpad in the future, we might
have to check whether the option creates a problem.
|
| |
|
|
|
|
| |
Apparently one of its python dependencies went EOL and everything went
to fuck because python is a crapfest and nixpkgs policies around it
are stupid. yay.
|
| | |
|
| |
|
|
|
| |
This is not pretty, some of the code lives in vuizvui, some lives in
tvl depot. But at least it seems to work for now :)
|
| |
|
|
| |
though the backup service is broken on the machine anyway, idk
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Changes the weechat setup so that I can have multiple instances, each
gets their own unix user & separate weechat instance.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
It’s only checked at the end LOL
|
| |
|
|
|
| |
Upstream is dumb, but the tool is certainly useful, so let’s patch it
to make it workable and then also patch the nixos module …
|
