| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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
|
|
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
|
|
Python 3.3 reaches end-of-life when we release 17.09.
https://mail.python.org/pipermail/python-dev/2017-July/148584.html
|
|
cc #25980
|
|
BundlerEnv, now with groups and paths
|
|
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.
|
|
These packages have been broken for a while and now they don't even evaluate
any more.
|
|
|
|
|
|
matthewbauer/nixpkgs-manual-declarative-package-management
manual: add "declarative package management" section
|
|
|
|
|
|
|
|
Purge stdenv cross
|
|
|
|
doc / go building: improve
|
|
Move the paragraph about go2nix to the other paragraphs about dependencies.
|
|
Get rid of gcc-cross-wrapper
|
|
Packages get --host and --target by default, but can explicitly request
any subset to be passed as needed. See docs for more info.
rustc: Avoid hash breakage by using the old (ignored)
dontSetConfigureCross when not cross building
|
|
erlang: refactor: build packages per Erlang/OTP version.
|
|
|
|
Improve beam docs:
* correct spelling
* update per pandoc changes
* capitalize titles
* capitalize BEAM throughout and use "the BEAM" when referring to the virtual machine.
* tweak grammar and phrasing
* reformat build-tools-rebar3 section
* add more links
* re-wrap <para>s
Also update <programlisting>s
* normalize whitespace
* don't double quote homepage
* use $ in all shell snippets
|
|
The documentation got a bit stale compared to actual contents of
nixpkgs. This commit focuses on updating existing docs, not on making
sure all details of beam packages are covered.
|
|
nixpkgs manual: advise against overriding whole phases
|
|
|
|
It is no longer necessary to wrap Qt packages
|
|
manual: add "Emacs" section to manual
|
|
|
|
|
|
I've seen that mistake at least a few times already, e.g.
https://github.com/NixOS/nixpkgs/pull/26209#issuecomment-305925562
It might perhaps seem counter-intuitive if one doesn't know nixpkgs well.
|
|
lib and doc: Use "libSystem" as identifier for that libc in platforms
|
|
|
|
lib: Consolidate platform configurations (used for crossSystem)
|
|
This is good for maintenance and education.
|
|
|
|
thanks to @bjornfor for catching this
|
|
These all should be uncontroversial changes. Just some awkward wording and
double words, etc.
|
|
This section gives some details on how to setup an "environment"
without having to go through NixOS (although it could be used there
too). I’ve tried to make it straightforward and have a kind of
"tutorial" feel. Not sure if that’s appropriate for the manual, so any
recommended changes would be helpful.
|
|
This gives some basics on configuring Emacs within Nix. The
configuration is fairly long just to give a good idea of what’s going
on. I can trim out some of it if it’s not necessary. Note that there
is already a section for Emacs in the NixOS manual. However, this is
aimed at avoiding using modules altogether to make things easier for
non-NixOS users. This configuration should work on NixOS anyway,
however.
Fixes #24243
Fixes #19956
|
|
|
|
See f63eb5857352705665411130d4f1638d55dd8c58
The `requests2` attribute now throws an error informing that `requests`
should be used instead.
|
|
Use "fenced" code blocks to enable syntax highlighting. Other markup
and formatting.
|
|
PR #815 has already been cherry-picked into the default nix version 1.11.8.
|
|
Changes to nixpkgs infra to prepare to better package some pesky cross-compilers
No hashes (native or cross) should be changed
|
