| Commit message (Collapse) | Author | Age |
... | |
| |/ /
|/| |
| | |
| | | |
Refer to doubles.nix for a list of common platforms types used in packages
|
|\ \ \
| | | |
| | | | |
Weechat plugin split
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Also add a wrapper generator that allows adding the plugins back
conveniently and corresponding documentation in the package notes
section of the nixpkgs manual.
|
| | | | |
|
|/ / /
| | |
| | | |
The nix-shell command here is incorrect AFAICT. `-i` is supposed to specify the interpreter and `-p` specifies the packages.
|
| | |
| | |
| | |
| | | |
Resolves confusion mentioned in #31045.
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The biggest benefit is that we no longer have to update the registry
package. This means that just about any cargo package can be built by
nix. No longer does `cargo update` need to be feared because it will
update to packages newer then what is available in nixpkgs.
Instead of fetching the cargo registry this bundles all the source code
into a "vendor/" folder.
This also uses the new --frozen and --locked flags which is nice.
Currently cargo-vendor only provides binaries for Linux and
macOS 64-bit. This can be solved by building it for the other
architectures and uploading it somewhere (like the NixOS cache).
This also has the downside that it requires a change to everyone's deps
hash. And if the old one is used because it was cached it will fail to
build as it will attempt to use the old version. For this reason the
attribute has been renamed to `cargoSha256`.
Authors:
* Kevin Cox <kevincox@kevincox.ca>
* Jörg Thalheim <Mic92@users.noreply.github.com>
* zimbatm <zimbatm@zimbatm.com>
|
| | |
|
|\ \
| | |
| | |
| | | |
Very many rebuilds from master :-(
|
| | |
| | |
| | |
| | |
| | | |
I didn't notice the cherry-pick, but Globin found out immediately.
/cc #29180.
|
| | |
| | |
| | |
| | | |
/cc #29180.
|
|\| | |
|
| | | |
|
|/ / |
|
|/
|
|
|
|
|
| |
Commit 8537cf0f818a95073e93ac755e9fa17c30982caa
("CONTRIBUTING.md: suggest "nixos/<module>" prefix for NixOS changes")
only changed CONTRIBUTING.md file and forgot about the Nixpkgs manual.
(I didn't know this information was stored in two places.)
|
|
|
|
|
| |
Applying `haskell.lib.failOnAllWarnings` to a Haskell package enables the
`-Wall` and `-Werror` GHC options to turn all warnings into build failures.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
- fix some mistakes
- move explanation on how to create Python environments to the front
|
|\ |
|
| |\ |
|
| |\ \ |
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Because if you were to disable man pages via 'programs.man.enable',
the "man" output wouldn't be installed and the info pages would go
missing.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Because .doc is normally not installed to user environments, these
manpages are unaccessible by default otherwise.
|
| |\ \ \ \
| | |/ / /
| |/| | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The main motivation for this is to have something to google for LD=$CC.
Eventually, this should probably be moved to another section, but we
can deal with that later.
|
| |_|_|/
|/| | | |
|
| |_|/
|/| |
| | |
| | | |
1. Call `nix-build` with `--no-out-link` to avoid cluttering the source dir.
2. Re-add `patchShebangs`, since `buildCommand` doesn't imply a patch phase. (It was my fault to remove this in the first place, sorry!)
|
|\| | |
|
| |\ \
| | | |
| | | | |
replace "Mac OS X" and "OS X" with "macOS"
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
as it is the official name since 2016
https://en.wikipedia.org/wiki/Macintosh_operating_systems#Desktop
exception are parts refering to older versions of macOS like
"GUI support for Mac OS X 10.6 - 10.12. Note that Emacs 23 and later [...]"
|
| | | | |
|
| |_|/
|/| | |
|
|/ /
| |
| |
| |
| |
| | |
to better fit the existing naming scheme.
https://github.com/NixOS/nixpkgs/pull/26155#issuecomment-321279629
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows one to always override the call to `buildPythonPackage`.
In the following example we create an environment where we have the `blaze` package using an older version of `pandas`. We override first the Python interpreter and pass `packageOverrides` which contains the overrides for packages in
the package set.
```
with import <nixpkgs> {};
(let
python = let
packageOverrides = self: super: {
pandas = super.pandas.overridePythonPackage(old: rec {
version = "0.19.1";
name = "pandas-${version}";
src = super.fetchPypi {
pname = "pandas";
inherit version;
sha256 = "08blshqj9zj1wyjhhw3kl2vas75vhhicvv72flvf1z3jvapgw295";
};
});
};
in pkgs.python3.override {inherit packageOverrides;};
in python.withPackages(ps: [ps.blaze])).env
```
|
| |
| |
| | |
The 'phases' attribute is unneeded and misleading
|
|\ \
| | |
| | | |
python33: end-of-life
|
| | |
| | |
| | |
| | |
| | |
| | | |
Python 3.3 reaches end-of-life when we release 17.09.
https://mail.python.org/pipermail/python-dev/2017-July/148584.html
|
| |/
|/|
| |
| |
| | |
1. 'wrapper' has been renamed to 'wrappedRuby', so use this instead.
2. mkDerivation isn't called with a 'src' attribute, so skip the 'unpackPhase' to avoid an error.
3. Simplify the build command. 'mkdir' and 'patchShebangs' don't need to be called explicitly.
|
| | |
|
| | |
|
|\ \
| |/
|/| |
fzf: add script for finding 'share' folder
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
So that helper scripts can be easily sourced in interactive shell
configuration. `autojump` package was already present and had the same
requirements for findind a `share` folders, so I took an inspiration
there.
I beleive this is a better alternative to:
- https://github.com/NixOS/nixpkgs/pull/25080
- https://github.com/NixOS/nixpkgs/pull/27058
Replacing `$out/share/shell` with `$bin/share/fzf` was necessary to
prevent dependency loop in produced derivations.
|