Not saying something new but let me recap so that it’s maybe more obvious what is said.
It’s always a bad design to have a circular dependency, as you will never be able to bootstrap those packages and this problem is not nix related, it’s an issue when trying to build the library isolated. You need one of those already build externally to be able to build the other. Nix is just enforcing the isolation.
A common way of solving a circular dependent is to externalize the common function (which make them depend on each other is the circle), so that you can build that Library first and then can build the two other packages independently).
If the libraries are your own, you could adapt the source code, if they are not yours, youwill not be able to build from source isolated. You could grab them possibly from pip if they are available there.
I get it now, thanks for the explanation.
unfortunately the packages are not mine, and it will take a long time to solve this problem, so I don’t think the developer will do it…
Yes they are available in pip, but I don’t like that solution. As far as I’ve heard building from non-source is not exactly the Nix way… I’ll leave those packages aside for now