| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
Pscycopg2-binary is normally used in Python development to avoid having to build psycopg2 from source.
In nixpkgs we always want ot build from source whenever possible, but it can still be useful to provide a psycopg2-binary package.
This "fake" package exists to satisfy a dependency on psycopg2-binary, but still use the build from psycopg2.
cc @misuzu https://github.com/nix-community/pyproject.nix/issues/143
|
|
`importNpmLock.buildNodeModules` returns a derivation with a pre-built `node_modules` directory, as imported by `importNpmLock`.
This is to be used together with `importNpmLock.hooks.linkNodeModulesHook` to facilitate `nix-shell`/`nix develop` based development workflows:
```nix
pkgs.mkShell {
packages = [
importNpmLock.hooks.linkNodeModulesHook
nodejs
];
npmDeps = importNpmLock.buildNodeModules {
npmRoot = ./.;
inherit nodejs;
};
}
```
will create a development shell where a `node_modules` directory is created & packages symlinked to the Nix store when activated.
This code is adapted from https://github.com/adisbladis/buildNodeModules
|
|
This function exists create a meta package containing [metadata files](https://packaging.python.org/en/latest/specifications/recording-installed-packages/) to satisfy a dependency on a package, without it actually having been installed into the environment.
|
|
This patch moves the code snippet which is shown as equivalent to the
example into the actual example block.
Visually, it was not easy to parse that the "equivalent" code piece
belonged to the code snippet that was hidden in the example (which is
collapsed by default).
By moving it into the example block, the "equivalent" piece is hidden by
default as well.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
|
|
Fixes https://github.com/NixOS/nixpkgs/issues/65252
|
|
nixpkgs-manual: Document `runCommandWith`, refactor `runCommand{,CC,Local}`
|
|
|
|
|
|
|
|
Co-authored-by: Johannes Kirschbauer <hsjobeki+github@gmail.com>
|
|
Co-authored-by: Johannes Kirschbauer <hsjobeki+github@gmail.com>
|
|
* vimPlugins: introduce passthru.initLua for some plugins
as described in https://github.com/NixOS/nixpkgs/issues/172538, some vim
plugins need some configuration to be able to work at all.
We choose not to patch those plugins and instead expose the necessary
configuration to make them work in `PLUGIN.passthru.initLua`.
For now the user can check if plugins have a `PLUGIN.passthru.initLua`
and if yes, prepend it to their own init.lua.
Maybe later we can revisit this to either patch them in a way that is
clear that it's a nixpkgs patch or by having the neovim wrapper pick
those snippets and autoadd them to init.lua ?
* Update doc/languages-frameworks/vim.section.md
Co-authored-by: Marc Jakobi <mrcjkb89@outlook.com>
---------
Co-authored-by: Marc Jakobi <mrcjkb89@outlook.com>
|
|
testers.runCommand: init
|
|
We haven't been good at managing expectations about this, so let's
tell people what level of support they can expect. I think the place
people are most likely to see it is the place where they learn about
overriding in the first place, so I've added it here.
Co-authored-by: Valentin Gagarin <valentin@gagarin.work>
|
|
|
|
rPackages: migrate code generation to use JSON
|
|
Conflicts:
- pkgs/development/python-modules/pycdio/default.nix
|
|
doc/README: Add function Inputs guidelines
|
|
doc/python: don't recommend all-packages.nix for Python applications
|
|
|
|
|
|
|
|
pnpm.fetchDeps: Add workspace and custom pnpm config commands support
|
|
|
|
|
|
pbsds/doc-python-auto-remove-deps-hook-1722967990
docs/language-frameworks/python: pythonRemoveDepsHook is added automatically
|
|
|
|
|
|
The hook relied on the `test` command passed to `setup.py`, which has
long been deprecated and finally removed in setuptools 72.0.
|
|
configuration commands
Solves #316908
|
|
|
|
dotnet: use unpacked packages in store
|
|
|
|
|
|
|
|
docs: show `pyproject = true;` instead of `format = "pyproject";`
|
|
grep -rP 'maintainers = \[\];'
|
|
`lib.trivial.revisionWithDefault` will change with every Git commit, which causes the manual to be rebuilt on every since PR.
Using `nixpkgs.rev` (or the dummy value "master" if it's not present) means that the manual will contain the revision if built on Hydra, but will not otherwise.
Why?
1. https://hydra.nixos.org/jobset/nixos/trunk-combined#tabs-configuration shows that `pkgs/top-level/release.nix` is passed the `nixpkgs` attrset, which is a "Git checkout".
2. Git checkouts come from [`builtins.fetchGit`](https://nix.dev/manual/nix/2.18/language/builtins#builtins-fetchGit) and include the `rev` attribute.
3. The `rev` attribute is what `lib.trivial.revisionWithDefault` would have returned.
So, using `nixpkgs.rev or "master"` exclusively will cause the rebuilds on every commit to cease, but will allow "official" nixpkgs manual built on Hydra to continue to reference a specific commit.
|
|
* doc/interoperability: new chapter and section on CycloneDX
|
|
|
|
|
|
cc-wrapper: add support for `shadowstack` hardening flag
|
|
|
|
|
|
nix-channel: do not set empty nix-path when disabling channels
|
|
|
|
|
|
|
