| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
This was accidentally removed when buildPython* was rewritten as hooks.
|
| |
|
|\
| |
| |
| | |
Earlier the gcc8 branch was merged instead of the gcc-8 branch (note the dash)...
|
| |\ |
|
| |\ \ |
|
| | | | |
|
|\ \ \ \ |
|
| |\ \ \ \
| | | | | |
| | | | | | |
php72: 7.2.21 -> 7.2.22
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Changelog: https://www.php.net/ChangeLog-7.php#7.2.22
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
See https://bugs.ruby-lang.org/issues/16136.
This patch is on Ruby trunk, but hasn't been backported (yet?).
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This has been EOL since December. We shouldn't still be facilitating
its use.
Fixes https://github.com/NixOS/nixpkgs/pull/67977.
|
|\| | | | |
|
| |\ \ \ \
| | | | | |
| | | | | | |
php73: 7.3.8 -> 7.3.9 (security)
|
| | | |_|/
| | |/| |
| | | | |
| | | | |
| | | | |
| | | | | |
https://www.php.net/archive/2019.php#2019-08-29-1
https://www.php.net/ChangeLog-7.php#7.3.9
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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`).
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | | |
|
|\| | | | |
|
| |\ \ \ \
| | |/ / /
| |/| | | |
supercollider: 3.10.2 -> 3.10.3
|
| | | | |
| | | | |
| | | | |
| | | | | |
Changelog: https://github.com/supercollider/supercollider/releases/tag/Version-3.10.3
|
| | | | |
| | | | |
| | | | |
| | | | | |
Co-authored-by: Alyssa Ross <hi@alyssa.is>
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |/ / / |
|
| | | | |
|
|\| | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Lua packages now consistently use LUA_PATH/LUA_CPATH rather than a mix
of those and NIX_LUA_PATH/NIX_LUA_CPATH
- Lua libraries are now consistently only added to the search path
variables if:
1) The library actually has a corresponding directory to search
2) The library is not already present in the search path
This should help prevent the search paths from growing overly large
- Fixed bugs in some path helpers
- Changed the affected shell script indentation to 2 spaces; nixpkgs
shell scripts are inconsistently split between 2 and 4 space
indentation, but 2 matches better with the Nix expressions, so IMO it
makes more sense
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Our sqlite supports it, so might as well make use of it.
Fixes #66526
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
|\| | | |
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Nix repl hangs when evaluating empty files.
find -name "*.nix" -empty -delete
|
| | | | |
| | | | |
| | | | |
| | | | | |
https://github.com/google/evcxr/releases/tag/v0.4.4
|
| | | | | |
|
|\| | | | |
|
| |\| | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes #67200
(cherry picked from commit 302cac35f586d0cc4813ae0cf5d124f1375deecf)
|
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We don’t want cpython picking up /Library/Frameworks and
/System/Library/Frameworks which contains Tcl.framework. Instead it
should use the one provided by Nix. this would not be an issue if
sandboxing was enabled, but unfortunately that has its own issues.
Fixes #66647
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
There were several more conflicts from name -> pname+version;
all auto-solved by kdiff3, hopefully OK.
Hydra nixpkgs: ?compare=1538611
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The current version fails to build: https://hydra.nixos.org/build/99189245
Please note that the releases aren't tracked by Git, but the currently
used rev points to `0.4.3` at crates.io: https://crates.io/crates/evcxr/0.4.3
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
There ver very many conflicts, basically all due to
name -> pname+version. Fortunately, almost everything was auto-resolved
by kdiff3, and for now I just fixed up a couple evaluation problems,
as verified by the tarball job. There might be some fallback to these
conflicts, but I believe it should be minimal.
Hydra nixpkgs: ?compare=1538299
|
| | |\ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Per https://www.php.net/manual/en/intro.mhash.php, mhash extension
is obsolete, so disabling it here. (Also it doesn't cross-compile)
**Warning**: This could be a breaking change for some packages that
are very old and rely on this extension, maintainer discretion is
advised.
|