@GrahamcOfBorg build google-drive-ocamlfuse

@anmonteiro Seems like this beak google-drive-ocamlfuse as mentioned in the linked thread. This probably could be fixed by packaging extlib-compat and using it for google-drive-ocamlfuse.

Thanks, @sternenseemann. I'm OK waiting for the final deliberation in ocaml/opam-repository#17999 (comment) before this gets merged.

The option the opam-repository took is to simply patch 1.7.7: ocaml/opam-repository#18041.
I'm not sure how NixOS deals with conflicts but since extlib and extlib-compat are incompatible it was not the right solution for us.

Furthermore the compat version adds more incompatible modules than previous version of extlib so I would suggest not to use it in NixOS.

Thanks, Kate! I think taking the same approach and using your patches here could work. I'll look into that later today.

Note that the two patches I cherry-picked were taken from the upstream's master branch: ygrek/ocaml-extlib#55

haxe 4.0.x and 4.1.x need extlib 1.7.7 but haxe 4.2.0 needs extlib 1.7.8
it seems that we need both

haxe 4.0.x and 4.1.x need extlib 1.7.7 but haxe 4.2.0 needs extlib 1.7.8
it seems that we need both

Maybe the upstream patches would apply cleanly on the older versions? Then we wouldn't need to keep two extlib versions around.

haxe 4.0.x and 4.1.x need extlib 1.7.7 but haxe 4.2.0 needs extlib 1.7.8
it seems that we need both

Maybe the upstream patches would apply cleanly on the older versions? Then we wouldn't need to keep two extlib versions around.

Actually, I do not think older Haxe's are worth including in official nixpkgs, haxe 4.2.0 + extlib 1.7.8 is good enough.

I added all the intermediate versions to local nixpkgs just to bisect problems migrating from 3.4.x

Then we probably should do the haxe update in this PR as well.

Then we probably should do the haxe update in this PR as well.

#95638 (comment)

just remove extlib-1.7.7 and haxe versions which depend on it (4.0.x and 4.1.x)

See also #116953.

closed in favor of #117113