Repository navigation
Relax mozjs_icu_normalizer's icu_properties requirement - #836
Conversation
90182d5 to
bf33637
Compare
|
Would it be enough to just relax the version requirement here, because as far as I can tell we still use it via other crates, but I guess they are not problematic because of less strict semver? |
|
Ah yes relaxing it works too. I'll push a fix to do that. I'm compiling without the |
bf33637 to
1573cd0
Compare
|
We need to test this in servo before landing too as some earlier experiments showed problems #831 (comment) |
BTW this only changes the version requirement if the |
To verify this I pulled servo and pointed it to this commit and the lockfile is unchanged after regeration, so this only helps folks like me who disable |
222cd38 to
352f84f
Compare
|
Gentle ping |
SpiderMonkey never enables the normalizer's optional icu_properties dependency, but Cargo still locks optional dependencies that weak `icu_properties?/...` features refer to. Its `~2.1.1` requirement then pins icu_properties for every crate that depends on mozjs, so a crate that also needs ICU4X 2.2 or later (for example through icu_collator) fails to resolve, even with the intl feature off. update.py now rewrites the requirement to a caret `2.1.1` when it extracts the crate. Signed-off-by: Tyler Rockwood <rockwotj@gmail.com>
352f84f to
b6549e1
Compare
|
thanks all! |
SpiderMonkey never enables the normalizer's optional icu_properties
dependency, but Cargo still locks optional dependencies that weak
icu_properties?/...features refer to. Its~2.1.1requirement thenpins icu_properties for every crate that depends on mozjs, so a crate
that also needs ICU4X 2.2 or later (for example through icu_collator)
fails to resolve, even with the intl feature off.
update.py now rewrites the requirement to a caret
2.1.1when itextracts the crate.
Testing: We're using this at Tasklet in a WASM build to successfully
run
mozjs, this is needed because we have another crate that usesICU but the versions conflict.