 | Nix PHP | 71 Members |
| A room for PHP developers running on Nix | 22 Servers |
| Nix PHP | 71 Members |
| A room for PHP developers running on Nix | 22 Servers |
| Sender | Message | Time |
|---|---|---|
| 2 Mar 2022 | ||
 Pol | * ramsey: I would like to push a change for PHP in Nix. Basically, I would like to replace the src URL in PHP extensions. I would like to change from using the URL provided by PECL to using the Git repository directly. Like that, we slowly move away from PECL and use Git exclusively and also, it can be picked up by the automatic updater (r-ryantm) bot to make sure that packages are always up-to-date. What do you think of that? Is PECL still used that much? Is it a good idea to slowly move away from it? Are there any drawbacks by doing such thing? | 08:36:33 |
| 3 Mar 2022 | ||
 ramsey | In reply to @drupol:matrix.orgPECL is still the primary way to distribute PHP extensions, and I’ve not heard anything about it going away anytime soon. There is a separate project called “pickle” that can take the place of PECL, though. I think whether the PHP project retires PECL depends on having someone come along who can propose a process for moving to something else and dedicate time and energy to making it happen. | 02:13:41 |
| ramsey | https://github.com/FriendsOfPHP/pickle | 02:14:26 |
| Pol | But pecl relies on an external Git repo, right? It does not provide its own. | 06:17:45 |
| Pol | I'm trying to add a feature to generic.nix so we will be able to compile the development branch of PHP. I did this: https://github.com/NixOS/nixpkgs/compare/master...drupol:feat/let-php-compile-master-branch and it seems to work locally. It's building the branch master right now. But I'm wondering if this is the best way to do that. I see in the bottom of the file that there is a way to override some attributes, maybe I should do that. WDYT ? | 17:20:45 |
| Pol | Maybe I can do that with overrideAttrs but I'm having hard time finding how to use it. | 17:27:03 |
| Pol | I think I have it: | 17:30:28 |
| Pol |  Download image.png | 17:30:30 |
| Pol | Nope. | 17:32:05 |
| 4 Mar 2022 | ||
| Pol | Right, I closed this issue https://github.com/NixOS/nixpkgs/pull/158098 as we were not aligned on how it should be done. | 15:05:41 |
| 5 Mar 2022 | ||
| ramsey | Not sure why I’m not getting notifications from Element. Pol: I’m not sure what you mean by “pecl relies on an external Git repo.” I’m also don’t understand what that has to do with compiling the development branch of PHP. PHP has multiple development branches, btw. PHP-7.4 has 7.4.x-dev, PHP-8.0 has 8.0.x-dev, and PHP-8.1 has 8.1.x-dev. I think the master branch currently shows 8.2.x-dev. | 21:28:04 |
| Pol | ramsey: No worries, I closed the issue. Basically, all the PHP extensions in Nix are relying on PECL urls to downloads src. I wanted to change that and use GitHub exclusively so r-ryantm bot could pick up those projects and provide automatic PRs to update them when a tag is published. I closed the issue for 2 reasons. First reason is that I haven't got much support from Nix PHP maintainers, and secondly because it turns out that the bot already update those packages (maybe there was an update in the meantime). Regarding PHP development branches, this is another thing. I'm trying to build PHP from a dev branch and I will try those branches as well. I'm new to Nix (10 month), so there are things that I do not fully understand yet. | 21:45:08 |
| 8 Mar 2022 | ||
 finn joined the room. | 16:11:02 | |
| finn left the room. | 16:11:56 | |
| 10 Mar 2022 | ||
 etu | The majority of extensions are upstream extensions and built from the same source as the php distribution though :) | 07:11:57 |
| 12 Mar 2022 | ||
| ramsey | In reply to @drupol:matrix.orgI'm newer to Nix (< 1 month), so you know a lot more about it than I do. 😉 | 20:00:13 |
| Pol | It's fine :D we're both newcomers! | 20:00:29 |
| Pol | If you need anything, just ask, I'll try to help as best as I can. | 20:00:41 |
| ramsey | Pol: Just stumbled across this PR: https://github.com/NixOS/nixpkgs/pull/158098 | 22:17:06 |
| ramsey | I think it would be great to add Phive to the list of PHP tools (along with Composer) | 22:17:23 |
| ramsey | I'm trying to set up a development environment with nix pkgs, and Phive is one of the tools I need in that environment 🙂 | 22:18:18 |
| ramsey | Phive cannot be installed via Composer, so I have to manually download an install it | 22:19:11 |
| ramsey | * Phive cannot be installed via Composer, so I have to manually download and install it | 22:19:19 |
| ramsey | Also, it's becoming increasingly popular (and more reliable) to use the Phar versions of tools like PHPUnit, Psalm, PHPStan, etc., but the phar versions can't be added to require-dev and installed using Composer, so you have to download them individually for your dev environment | 22:22:29 |
| ramsey | Phive helps us do this, so I'd be fine excluding PHPUnit, Psalm, PHPStan, etc. from Nix packages, as long as Phive is provided, so that we can easily download them for the environment | 22:23:20 |
| ramsey | Although, there is this, which might allow installing Phars with Composer: https://packagist.org/packages/phar-io/composer-plugin | 22:24:38 |
| Pol | I will focus on this tomorrow, it was on my to-do list! | 22:24:39 |
| ramsey | So, if that package does the trick, then even adding a separate nix package for Phive might not be necessary | 22:25:05 |
| ramsey | except they haven't updated it for the latest version of Composer, so it won't install ☹️ | 22:26:16 |
| Pol | In reply to @ramsey:matrix.orgI fully agree. Some of those packages provide a SHIM version and it's just enough | 22:27:02 |