Overview
Request 1200811 superseded
so I am not 100% sure if that actually should work. but because upstream changed how they name SONAME, we now have a conflict between the older and this version (as they ship {.so,.so.0,so.0.{22,23}}. Do I need to Conflict the older libtree-sitter0?
- update to 0.23.0:
* test: modernize scanner files
* fix: always reset to the first language when iterating over language
* feat(zig): update outdated path syntax
* feat(bindings): add query constants to python
* style(bindings): fix indent & line endings
* feat(dsl)!: support other JS runtimes
* feat(bindings): add node, python, swift tests
* introduce tree-sitter-language crate for grammar crates to depend on
* refactor: remove ansi_term dependency
* refactor: remove difference dependency
* feat: add fuzz subcommand
* fix(wasm): update test
* feat(lib): add ts_query_end_byte_for_pattern
* fix(rust): fix new clippy warnings
* feat(lib): support no_std
* Reset language when resetting wasm store
* docs: clean up binding & parser lists
* clone wasm store engine
* fix(cli): dedup preceding_auxiliary_symbols
- use of ldconfig_scriptlets, and removal of the duplicate setting of buildflags
- Created by rrahl0
- In state superseded
-
Package maintainer:
Thaodan
- Superseded by 1201293
Request History
rrahl0 created request
so I am not 100% sure if that actually should work. but because upstream changed how they name SONAME, we now have a conflict between the older and this version (as they ship {.so,.so.0,so.0.{22,23}}. Do I need to Conflict the older libtree-sitter0?
- update to 0.23.0:
* test: modernize scanner files
* fix: always reset to the first language when iterating over language
* feat(zig): update outdated path syntax
* feat(bindings): add query constants to python
* style(bindings): fix indent & line endings
* feat(dsl)!: support other JS runtimes
* feat(bindings): add node, python, swift tests
* introduce tree-sitter-language crate for grammar crates to depend on
* refactor: remove ansi_term dependency
* refactor: remove difference dependency
* feat: add fuzz subcommand
* fix(wasm): update test
* feat(lib): add ts_query_end_byte_for_pattern
* fix(rust): fix new clippy warnings
* feat(lib): support no_std
* Reset language when resetting wasm store
* docs: clean up binding & parser lists
* clone wasm store engine
* fix(cli): dedup preceding_auxiliary_symbols
- use of ldconfig_scriptlets, and removal of the duplicate setting of buildflags
superseded by 1201293
The older libtree-sitter0 will be obsolete as it can be no longer provided by the repositories in most cases that should be enough I think. I'm neither sure what happens when a user has a package that depends on libtree-sitter0 but also upgrades a package that depends on the version that has a sover now.
Besides that question your changes LGTM.