wireplumber 0.5

[arcnmx]

New major version!

• [ ] finish and get it compiling
  • [x] logging api changes
  • [ ] deprecate/rework log domain: syntax; it's called a "topic" now
  • [x] core changes
  • [ ] config/lua changes
  • [x] process GBoxed lua script args
  • [x] SpaJson deserializer
  • [x] impl serde::Deserializer for SpaJson (wrapper around existing &SpaJson impl)
  • [ ] impl serde::Deserializer for SpaJsonParser (complicated by a need to know which constructor the parser was created with...)
    • [ ] and &mut SpaJsonParser wrapper impl
  • [x] SpaJson/SpaJsonBuilder serializer
  • [x] impl serde::Serialize for SpaJson
  • [x] impl serde::Deserialize for SpaJson
  • [ ] serde and parser test cases
  • [ ] clean up lua table types and conversions?
  • [ ] plugin/loader changes
  • [x] plugin subclassing
  • [ ] component loader interface impl
• [ ] go over all new types
  • [ ] Global and ObjectManager::add_global?
  • [ ] make sure they're re-exported in appropriate modules
• [ ] move signals into crate::events module
• [ ] new members and functions exposed properly etc
  • [ ] LibraryErrorEnum::ServiceUnavailable new variant/constructor/etc
• [x] rebase onto #36
• [ ] test things!!!
  • [ ] port/update some existing downstream crates and applications to validate
• [ ] remove all outdated cfg version checks
• [ ] maintenance branch for wp 0.4
  • [ ] alternatively, gir-generate for both versions?
  • [ ] sys could possibly get away with exposing a v0_4 submodule?
  • [ ] alternate main crate would just include/#[path] shared code
  • [ ] backport SpaJson serde impls and related changes

[Gustash]

@arcnmx now that Fedora 40 released, and is targeting wireplumber 0.5, we really need proper support for 0.5 for our build system.

How much work is there left for this? Is there something I can do to help speed this up?

[arcnmx]

Sorry this has been so delayed. There's still probably going to be lots of churn but the port to 0.5 is starting to come together now in the wp-0.5 branch.