Hey Georges, thanks for the detailed explanation! So I incorrectly assumed that setting persistent-nodemap.slow-path to `warn` was not, in fact, going to run some undesirable pure-Python implementation, but would actually entirely skip that feature, as if it had never been enabled. I guess it's not possible because of what you say here:
> And of course, disabling the persistent nodemap and re-enabling it is > making an inconsistent repository. Think of what could happen in a > mixed systems environment using some remote mounts, where some would > have the Rust extension, and some would not (perhaps because their > platform does not have a Rust toolchain). This is probably not what > could happen in sr.ht, but Mercurial has to think of such use cases > as well. I don't understand the problem completely, but I get the feeling it's something along the lines of "changeset IDs aren't deterministic so two identical repos could have different persistent-nodemaps and a client would get confused when talking to one and then talking the the other"? Or something like that? Anyway, I guess we'll have to consider circumventing the Alpine package and do our own install of Mercurial, similar to how you do it in Heptapod... Cheers! Ludo _______________________________________________ Mercurial mailing list Mercurial@lists.mercurial-scm.org https://lists.mercurial-scm.org/mailman/listinfo/mercurial
