| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Manually calling `mvn2nix` was the preferred way of building
Java apps that use Maven, but `maven.buildMavenPackage` is now the
preferred way.
|
|
Conflicts:
- pkgs/development/libraries/science/astronomy/cfitsio/default.nix
|
|
doc/contributing: update build instructions after nrd
|
|
|
|
|
|
|
|
|
|
nixpkgs/NixOS manuals: devmode feature
|
|
Respect global config.cudaSupport
|
|
We have moved away from Make since nixos-render-docs was introduced to
build the nixpkgs manual in #239636.
|
|
Co-authored-by: Alejandro Sanchez Medina <alejandrosanchzmedina@gmail.com>
|
|
Co-authored-by: Shahar "Dawn" Or <mightyiampresence@gmail.com>
|
|
nixos/fonts: rename fonts.fonts option to fonts.packages, other cleanups
|
|
docs/python: clarify allowance of using toosl to autogenerate packages
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
doc/reviewing-contributions: Add points about patches
|
|
Conflicts:
- pkgs/tools/networking/shadowfox/default.nix between e989daa65f2dd9827d56bee6a14a1965471f0597 and 1c29673fcce3aecd0cb4f30058c266ea5480c8a3
- pkgs/tools/networking/wuzz/default.nix between 7d80417710a9077b9142b479b02d07200d71d9db and 1c29673fcce3aecd0cb4f30058c266ea5480c8a3
|
|
|
|
In 787af0f79f128cb21b113d2eb37e64d913f18aae
I had to change ${go-modules} to $goModules to allow overrideAttrs to work;
However, env vars cannot contain -, so i had to change go-modules too.
This in turn broke nix-update because it uses the go-modules attr.
Instead of making nix-update more complicated, make go-modules naming match cargoDeps.
`fd --type f | xargs sd '\bgo-modules\b' 'goModules'`
and revert change to pkgs/applications/misc/dstask/default.nix
and pkgs/servers/http/dave/default.nix
and pkgs/os-specific/darwin/plistwatch/default.nix
release note added
|
|
Co-authored-by: Shahar "Dawn" Or <mightyiampresence@gmail.com>
|
|
|
|
doc: Render lib.fixedPoints
|
|
|
|
buildFHSEnv: disable multiArch by default
|
|
buildNpmPackage: add npmWorkspace and npmPruneFlags args
|
|
|
|
|
|
doc: dedocbookify nixpkgs manual
|
|
separating function docs out like this makes it less clear how library
documentation is generated and integrated into the build. if in the
future more parts of nixpkgs use nixdoc it will make sense to have all
information about library doc generation in the same place.
|
|
this leaves doc-support as a simple wrapper around function docs. this
wrapper will go away very soon as well.
|
|
all xml-related tooling can go away. shell.nix is no longer useful since
the makefile is gone and the build runs entirely via a derivation, and
gitignore is thus also no longer that useful. it may filter out some
swap files, but its main reason to exist (keeping generated files out of
a concurrent build of the derivation) has gone away.
|
|
also updates nixdoc to 2.3.0. the nixdoc update is not a separate commit
because that would leave the manual build broken for one commit,
potentially breaking bisects and rebases.
|
|
nothing except function docs uses this, so we need not expose it. we'll
be reworking this entire section of the build anyway, with the target of
breaking up doc-support as it is now.
|
|
mostly to clean up the main manual build makefile and derivation a bit.
not technically necessary, but will make life easier later.
|
|
stdenv: let overrideAttrs accept attrset OR function
|
|
|
|
The intention is to allow the user control over whether 32bit deps are supposed
to be included in the fhsenv
|
|
|
|
Makes overrideAttrs usable in the same way that `override` can be used.
It allows the first argument of `overrideAttrs` to be either a function
or an attrset, instead of only a function:
hello.overrideAttrs (old: { postBuild = "echo hello"; })
hello.overrideAttrs { postBuild = "echo hello"; }
Previously only the first example was possible.
Co-authored-by: adisbladis <adisbladis@gmail.com>
Co-authored-by: matthewcroughan <matt@croughan.sh>
|
|
|
|
This is actually relatively complicated to achieve, since it involves
overriding GHC on e.g. aarch64-darwin, so the FAQ entry seems warranted.
It's also a good exercise to me, since it demonstrates some problems
with the overriding infrastructure, i.e. that it has a tendency to
inherit the pkgs fixpoint from prev. An example of this problem is
https://github.com/NixOS/nixpkgs/issues/235960, but it has different
manifestations as well. Awareness of this will also help writing the
other sections on overriding.
How complicated it is, seems to be further incentive to go ahead with
https://github.com/NixOS/nixpkgs/pull/239548 as well.
|
|
|
