Open MSoegtropIMC opened 4 years ago
This way there would problems with packages that are in the main repo, but not yet in this repo: If foobar.1.2.3 requires patching and the main repo adds foobar.1.2.4, the version from the main repo would be used for some time and break the CIs for every packages that depends on foobar. (Similar issues would arise with depopts that are marked as unavailable in this repo).
I wonder if it wouldn't be better to organize the mingw opam repo such that it contains only thos packages which are different from the main opam repo. One could then initialite the repo with:
so that the mingw packages take precedence. This would increase usability since one would not have to wait until updates are ported. On the other hand it might make it a bit harder for the maintainers - one would have to teach git to ignore all common packages during merges.