| 26 Apr 2023 |
 Jan Tojnar | how are you cloning it? | 08:35:55 |
 Pol | I'm just using c4.composerFetchDeps, nothing else | 08:37:48 |
| Pol | In reply to @tgerbet:matrix.org
The composition-c4 way to fetch the deps is likely the best way in the sense it is not under the control of Composer so less likely to break It's using IFX (impure fixed derivation), and it's not allowed in nixpkgs. | 08:43:31 |
| Pol | In reply to @tgerbet:matrix.org
The composition-c4 way to fetch the deps is likely the best way in the sense it is not under the control of Composer so less likely to break * It's using IFD (impure fixed derivation), and it's not allowed in nixpkgs. | 08:43:40 |
| Pol | * It's using IFD (Import From Derivation), and it's not allowed in nixpkgs. | 08:44:28 |
 tgerbet | Yes but the idea behind composition-c4 is fine: fetching the deps without Composer to build a repository (this is the FOD) then using this repository when doing the install/dumpautoload parts | 08:46:24 |
| tgerbet | Not saying this is easy :p | 08:49:18 |
| Jan Tojnar | yeah, looks like it is another limitation of builtins.fetchGit, it should not be an issue if you replace it with a direct fetching | 08:55:18 |
| Pol | hum.... going to check that. | 08:55:41 |
| Pol | I replaced builtins.fetchGit with fetchgit but that doesn't seem to fix any issue. | 09:32:35 |
| Pol | no it's not. | 09:35:54 |
| Jan Tojnar | fetchgit will require a FOD hash, won’t it? I think you cannot get away from reimplementing the algorithm in something other than Nix | 09:56:42 |
| Pol | Oh man :( | 10:02:11 |
| Pol | So basically, you're telling me that I should write a script that would download all the dependencies with git, and then only we compute the hash on that ? | 10:02:42 |
| Jan Tojnar | yup | 10:03:19 |
