| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This reverts commit a1eacb900e1b705678b2c199cb97baafc9b77f86.
Adding dev outputs to python packages means they can't be included in
a Python environment created with python3.withPackages, because
makePythonPath will include the dev output, which is empty apart from
nix-support, rather than the out output, which contains all the Python
code.
|
| |
|
|
|
|
| |
This patch has not been necessary since
5425867bfa3e4ba83a3d67aa50b811b5f70d6fe5, and has in fact broken the
build since then.
|
| |
|
|
| |
This package is a dependency of GNU Mailman 3.3.x.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes
nix-shell -p 'ruby.withPackages (const [])' ruby.devdoc
which otherwise wouldn't find documentation, unlike
nix-shell -p ruby ruby.devdoc
which would, because ruby has setup hooks to accomodate for this, that
were being masked by the withPackages wrapper.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
sphinx has setuptools (pkg_resources) as a runtime-dependency
(cherry picked from commit 4de7d240b6d853c966cd001859f372e19d8a98e1)
|
| |
|
|
|
|
|
|
|
|
| |
As a side-effect of f7e28bf5d8181926e600a222cb70180519d09726, the build
no longer propagated 'setuptools', which is a run-time dependency. See
https://github.com/NixOS/nixpkgs/pull/68314 for further details.
Fixes https://github.com/NixOS/nixpkgs/issues/68479.
(cherry picked from commit b57f25ac805819b3b48635c1a59ae46b1ceb3468)
|
| |
|
|
|
|
|
|
| |
As a side-effect of f7e28bf5d8181926e600a222cb70180519d09726, the build
no longer propagated 'setuptools', which is a run-time dependency. See
https://github.com/NixOS/nixpkgs/pull/68314 for further details.
(cherry picked from commit 14854f20bb8002fa70828c820233ec05b177d04f)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit splits the `buildPythonPackage` into multiple setup hooks.
Generally, Python packages are built from source to wheels using `setuptools`.
The wheels are then installed with `pip`. Tests were often called with
`python setup.py test` but this is less common nowadays. Most projects
now use a different entry point for running tests, typically `pytest`
or `nosetests`.
Since the wheel format was introduced more tools were built to generate these,
e.g. `flit`. Since PEP 517 is provisionally accepted, defining a build-system
independent format (`pyproject.toml`), `pip` can now use that format to
execute the correct build-system.
In the past I've added support for PEP 517 (`pyproject`) to the Python
builder, resulting in a now rather large builder. Furthermore, it was not possible
to reuse components elsewhere. Therefore, the builder is now split into multiple
setup hooks.
The `setuptoolsCheckHook` is included now by default but in time it should
be removed from `buildPythonPackage` to make it easier to use another hook
(curently one has to pass in `dontUseSetuptoolsCheck`).
(cherry picked from commit f7e28bf5d8181926e600a222cb70180519d09726)
|
| |
|
|
|
|
| |
Fixes https://github.com/NixOS/nixpkgs/issues/68427.
(cherry picked from commit 26771ad0c52265fb13ed86743193f485920c37c6)
|
| |
|
|
| |
(cherry picked from commit aa6c38d9c162ecfc9c9f330ca65eb53de6d844c3)
|
| |
|
|
| |
This reverts commit d3983caf451ae52b2a527e6a9ad1620b950a8276.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This is no longer used in the expression, as it has been merged
upstream.
|
| |
|
|
| |
v# modified: nixpkgs/pkgs/tools/networking/dhcpcd/default.nix
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This should prevent problems caused by trying to install our own
RubyGems over the top of the one that comes with Ruby.
|
| |
|
|
|
|
| |
This works just fine, and means we don't run into an issue with RubyGems
trying to install into a different Ruby's prefix when cross-compiling.
See https://github.com/NixOS/nixpkgs/pull/51842#issuecomment-478392799.
|
| |
|
|
|
|
| |
Now that RI docs are installed to a seperate output, we don't need to worry
about bloating the main output, so it's reasonable for this to be enabled by
default.
|
| |
|
|
|
|
|
|
|
|
|
| |
This allows getting access to Ruby documentation through ri by doing
nix-shell -p ruby ruby.devdoc
or by installing the ruby.devdoc package.
A setup hook will add a shim to LOAD_PATH to point ri to the devdoc
output instead of out.
|
| |
|
|
|
| |
Even if building a Ruby with documentation, there's no reason for its
baseruby to waste time building its own documentation as well.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The pdfSupport option didn't feel necessary any more, since it depends
on zlib.
|
| | |
|
| | |
|
| | |
|