Age | Commit message (Collapse) | Author |
|
Fixes https://github.com/NixOS/nixpkgs/issues/204851
|
|
|
|
See https://github.com/NixOS/nixpkgs/issues/79303.
Avoids warnings about -fpermissive not being a valid C flag.
|
|
|
|
These versions don't build because their submodules use `git://` URLs,
which are no longer supported by GitHub.
I don't think there's a reasonable way to work around that since
`fetchgit` doesn't allow patching the source *before* fetching
submodules.
|
|
Updates the release number for the latest two DF versions, and fixes some
older ones.
Notable change from 0.47.05-r7: dfhack.init was moved into
dfhack-config/init.
https://github.com/DFHack/dfhack/releases/tag/0.47.05-r7
https://github.com/DFHack/dfhack/releases/tag/0.47.04-r5
|
|
Adds a `settings` argument to the wrapper allowing to override settings
in `data/init/*.txt`.
|
|
Currently, it is quite hard to override anything about dfhack (for
example, to add plugins at build time), because
1. it is not exposed anywhere, so you have to do something like
`dwarf-fortress.override (oldArgs: { dfhack = oldArgs.dfhack.override...; })`
2. the final `dfhack` derivation is a `buildEnv`, so `overrideAttrs`
doesn't work as expected.
This fixes 1 by adding `dfhack` to the wrapper's `passthru`, and 2 by
moving `twbt.lib` (which is the only reason for the dfhack `buildEnv`)
into the wrapper.
Also adds an `extraPackages` argument to the wrapper, and copies `*.init`
files from the env to the DF directory so that we can easily add a
`dfhack.init`.
With these changes, I was able to build dfhack with the dfplex plugin.
|
|
|
|
Avoid trying to build for aarch64 on Hydra. Dwarf Fortress only runs on x86.
|
|
|
|
|
|
|
|
|
|
Since the setting DCMAKE_SKIP_BUILD_RPATH was disabled, we can now run
the checkPhase of cmake derivations without having to tweak the
LD_LIBRARY_PATH anymore.
|
|
these are the easily identifiable cases and will not be comprehensive
|
|
|
|
|
|
|
|
I've tried to be consistent, using four or eight spaces to line up
with existing code.
|
|
lib.importJSON ./file.json
|
|
|
|
Otherwise you get an error upon starting the game:
```
Plugin twbt was not built for this version of DFHack.
Plugin: 0.47.05-beta1, DFHack: 0.47.05-r1
```
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- remove trailing whitespace
- use spaces for indentation
|
|
|
|
Part of: https://github.com/NixOS/nixpkgs/issues/108938
meta = with stdenv.lib;
is a widely used pattern. We want to slowly remove
the `stdenv.lib` indirection and encourage people
to use `lib` directly. Thus let’s start with the meta
field.
This used a rewriting script to mostly automatically
replace all occurances of this pattern, and add the
`lib` argument to the package header if it doesn’t
exist yet.
The script in its current form is available at
https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
|
|
|
|
dwarf-fortress: update themes.json
|
|
|
|
|
|
The original mifki TWBT hasn't been updated since April 2019, while
thurin's fork has added support for dfhack 0.47.04-r2. Thus, switch to
thurin's fork when Dwarf Fortress 0.47.04 is used (and ever-so-slightly
special case the url attribute).
|
|
dfhack expects an unversioned libruby.so to be present in the hack
subdirectory for ruby plugins to function. The glob is necessary,
because the ruby package's library names are formatted as
ruby-${version}.so for whatever reason. The glob makes it possible for
ruby to update without manual intervention being needed here.
|
|
As of
https://github.com/DFHack/dfhack/commit/56e43a0dde023c5a4595a22b29d800153b31e3c4,
dfhack gets its goodies from the directory above the Dwarf_Fortress
executable, which leads to stock Dwarf Fortress and not the built
environment where all the dfhack resources are symlinked to (typically
~/.local/share/df_linux). This causes errors like `tweak is not a
recognized command` to be reported and dfhack to lose some of its
functionality.
|
|
try hardcoding
add back whitespace
|
|
@the-kenny did a good job in the past and is set as maintainer in many package,
however since 2017-2018 he stopped contributing. To create less confusion
in pull requests when people try to request his feedback, I removed him as
maintainer from all packages.
|
|
tarballs.nixos.org is omitted from the change because urls from there
are always hashed and checked
|
|
|
|
|