| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
The package set is not maintained. It is also not used by most of the
BEAM community. Removing it to allow a more useful set of tools fit to
the BEAM community in Nixpkgs.
|
| |\
| |
| | |
buildStackProject: Set __noChroot to make it fail without sandbox
|
| | | |
|
| |/
|
|
| |
this had me stumped - thanks to adisbladis on irc
|
| |
|
|
| |
troubleshooting section to docs
|
| | |
|
| |\
| |
| | |
build-support/rust: Add target option
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Maybe there was an idea behind this separation, but looking at the
contents I don't see any reason for these being separate.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Reorganize the chapters into parts and reduce the TOC depth to make the
TOC useful again. The top-level TOC is very brief, but that is fine
because every part will have its own TOC.
Section titles of languages/frameworks are also simplified to just
the name of the language/framework.
|
| | |
| |
| |
| |
| | |
@garbas and @seppeljordan, are these updates correct?
I removed `offlinehacker/pypi2nix` as an unmaintained ancestor of the current repo `nix-community/pypi2nix`. It appears @garbas forked `offlinehacker/pypi2nix` to `garbas/pypi2nix` and then handed off maintainership to @seppeljordan, transferring the repo to `nix-community/pypi2nix`.
|
| |\| |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
One issue with cargoSha256 is that it's hard to detect when it needs to
be updated or not. It's possible to upgrade a package and forget to
update cargoSha256 and run with old versions of the program or
libraries.
This commit introduces `verifyCargoDeps` which, when enabled, will check
that the Cargo.lock is not out of date in the cargoDeps by comparing it
with the package source.
|
| | |
| |
| |
| | |
This reverts commit f8a8fc6c7c079de430fa528f688ddac781bcef16.
|
| | |
| |
| |
| |
| |
| |
| | |
This reverts commit 41af38f3728bd64b80721c44ed1fb019978cbc1b, reversing
changes made to f0fec244ca380b9d3e617ee7b419c59758c8b0f1.
Let's delay this. We have some serious regressions.
|
| | | |
|
| |/ |
|
| |\ |
|
| | | |
|
| |\| |
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| | |
doc: add GNOME
|
| | |
| |
| |
| | |
Examples are updated to commits that use them as well.
|
| | | |
|
| | |
| |
| |
| | |
Closes: #16285
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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`).
|
| |/
|
|
| |
Co-authored-by: Alyssa Ross <hi@alyssa.is>
|
| | |
|
| |\
| |
| | |
Androidenv fixes
|
| | |
| |
| |
| |
| |
| | |
This system type was previously broken but is now fixed.
Add it here to showcase the common task of launching a fully-fledged Android
system with an included app store.
|
| |/
|
|
|
|
|
| |
This setup hook modifies a Perl script so that any "-I" flags in its shebang
line are rewritten into a "use lib ..." statement on the next line. This gets
around a limitation in Darwin, which will not properly handle a script whose
shebang line exceeds 511 characters.
|
| | |
|
| |\
| |
| | |
add options for build idris package
|
| | | |
|
| |\ \
| |/
|/| |
Updating documentation about adding new Vim plugins
|
| | | |
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | | |
instead of into buildInputs
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
I merged this a bit too quick. We need to have a closer look at it.
See the points brought up in https://github.com/NixOS/nixpkgs/pull/64682.
This reverts commit 1e0ebdb8a4fe94db67b6520225d325292d60247c.
|
| |/ /
| |
| |
| | |
Flags passed to the "python setup.py" command.
|
| |\| |
|
| | |
| |
| |
| |
| | |
Not passing in the newly created interpreter as `self` results in an
incorrect `passthru`. Solves #64334.
|
| |/ |
|