| Commit message (Collapse) | Author | Age |
|---|
| |\ |
|
| | | |
|
| |/
|
|
|
| |
Using overrideSDK allows datadog_trace to use the correct SDK frameworks
even when they are propagated from curl.
|
| |\
| |
| | |
phpExtensions.php-spx: init at 0.4.14
|
| | | |
|
| |\ \
| |/
|/| |
phpExtensions.opcache: use valgrind only where supported
|
| | |
| |
| |
| |
| | |
opcache is a default extension, so this fixes eval of php on platforms
where valgrind is not supported, such as risc-v.
|
| | | |
|
| | |
| |
| |
| | |
Co-authored-by: Ember Keske <git@n0emis.eu>
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
version of PHP
|
| | |
|
| |\
| |
| | |
phpExtensions.mongodb: 1.15.0 -> 1.16.1
|
| | | |
|
| |/ |
|
| |\
| |
| | |
phpExtensions.inotify: update platforms
|
| | |
| |
| |
| | |
Follow up of https://github.com/NixOS/nixpkgs/pull/242015
|
| |/ |
|
| |
|
|
| |
The `inotify` extension is only available on Linux.
|
| |
|
|
|
|
|
| |
* php83: init at 8.3.0alpha2
* phpExtensions.blackfire: disable for php 8.3
* phpExtensions.apcu: patch for 8.3 only
|
| |
|
|
| |
This was missed in 84c0cb1471eee15e77ed97e7ae1e8cdae8835c61.
|
| |
|
|
|
|
|
|
|
|
| |
* phpExtensions.uv: init at 0.3.0
* Update pkgs/development/php-packages/uv/default.nix
---------
Co-authored-by: Joshua Trees <me@jtrees.io>
Co-authored-by: Pol Dellaiera <pol.dellaiera@protonmail.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
with structuredAttrs lists will be bash arrays which cannot be exported
which will be a issue with some patches and some wrappers like cc-wrapper
this makes it clearer that NIX_CFLAGS_COMPILE must be a string as lists
in env cause a eval failure
|
| |
|
|
|
| |
with structuredAttrs lists will be bash arrays which cannot be exported
which will be a issue with some patches and some wrappers like cc-wrapper
|
| |\
| |
| | |
phpExtensions.opcache: remove flaky test on darwin
|
| | |
| |
| |
| |
| | |
Some of the tests of ext-opcache are flaky on darwin.
Issue is not obvious to me and I cannot troubleshoot this locally.
|
| |\ \
| |/
|/| |
phpPackages.mkDerivation: use lib.{fix,extends} instead of //
|
| | |
| |
| |
| |
| |
| |
| | |
// on a overrideAttrs'able works badly
here we use lib.fix and lib.extends instead of overrideAttrs to have
less of a performance impact
|
| |/ |
|
| | |
|
| |
|
|
|
|
| |
enchant2 is supported in PHP8+.
Co-authored-by: Jan Tojnar <jtojnar@gmail.com>
|
| | |
|
| |\
| |
| | |
phpPackages.phan: init at 5.4.1
|
| | | |
|
| |/
|
|
| |
So they can be handled correctly by `nix-update` tool
|
| | |
|
| |\
| |
| | |
nextcloud25: use openssl 1.1 as a PHP extension to fix RC4 encryption
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Upon testing the change itself I realized that it doesn't build properly
because
* the `pname` of a php extension is `php-<name>`, not `<name>`.
* calling the extension `openssl-legacy` resulted in PHP trying to compile
`ext/openssl-legacy` which broke since it doesn't exist:
source root is php-8.1.12
setting SOURCE_DATE_EPOCH to timestamp 1666719000 of file php-8.1.12/win32/wsyslog.c
patching sources
cdToExtensionRootPhase
/nix/store/48mnkga4kh84xyiqwzx8v7iv090i7z66-stdenv-linux/setup: line 1399: cd: ext/openssl-legacy: No such file or directory
I didn't encounter that one before because I was mostly interested in
having a sane behavior for everyone not using this "feature" and the
documentation around this. My findings about the behavior with turning
openssl1.1 on/off are still valid because I tested this on `master` with
manually replacing `openssl` by `openssl_1_1` in `php-packages.nix`.
To work around the issue I had to slightly modify the extension
build-system for PHP:
* The attribute `extensionName` is now relevant to determine the output
paths (e.g. `lib/openssl.so`). This is not a behavioral change for
existing extensions because then `extensionName==name`.
However when specifying `extName` in `php-packages.nix` this value is
overridden and it is made sure that the extension called `extName` NOT
`name` (i.e. `openssl` vs `openssl-legacy`) is built and installed.
The `name` still has to be kept to keep the legacy openssl available
as `php.extensions.openssl-legacy`.
Additionally I implemented a small VM test to check the behavior with
server-side encryption:
* For `stateVersion` below 22.11, OpenSSL 1.1 is used (in `basic.nix`
it's checked that OpenSSL 3 is used). With that the "default"
behavior of the module is checked.
* It is ensured that the PHP interpreter for Nextcloud's php-fpm
actually loads the correct openssl extension.
* It is tested that (encrypted) files remain usable when (temporarily)
installing OpenSSL3 (of course then they're not decryptable, but on a
rollback that should still be possible).
Finally, a few more documentation changes:
* I also mentioned the issue in `nextcloud.xml` to make sure the issue
is at least mentioned in the manual section about Nextcloud. Not too
much detail here, but the relevant option `enableBrokenCiphersForSSE`
is referenced.
* I fixed a few minor wording issues to also give the full context
(we're talking about Nextcloud; we're talking about the PHP extension
**only**; please check if you really need this even though it's
enabled by default).
This is because I felt that sometimes it might be hard to understand
what's going on when e.g. an eval-warning appears without telling where
exactly it comes from.
|
| | | |
|
| |/ |
|