Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ability to parse D-Bus configuration file(s) #78

Open
zeenix opened this issue Apr 29, 2024 · 1 comment · May be fixed by #159
Open

Ability to parse D-Bus configuration file(s) #78

zeenix opened this issue Apr 29, 2024 · 1 comment · May be fixed by #159
Labels
feature parity Feature parity with existing bus impls

Comments

@zeenix
Copy link
Collaborator

zeenix commented Apr 29, 2024 •
edited
Loading

To be a drop-in replacement for the existing bus implementations, we need to be able to parse D-Bus XML configuration. Moreover, we should provide default files with easy method to install them as well (#77 should help with that).
@zeenix zeenix added the feature parity Feature parity with existing bus impls label Apr 29, 2024
This was referenced Apr 29, 2024
Open
Open
@jokeyrhyme
Copy link

Work on this is included in #23 and #146

@jokeyrhyme jokeyrhyme linked a pull request Oct 27, 2024 that will close this issue
Open
41 tasks
jokeyrhyme added a commit to jokeyrhyme/busd that referenced this issue Nov 30, 2024
@jokeyrhyme
🔧 Read Vec<Element> into consumer-ready Config
a1ddba0 
Fixes dbus2#78
Fixes dbus2#79
Fixes dbus2#148
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature parity Feature parity with existing bus impls
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

parse XML configuration files jokeyrhyme/busd
2 participants
@zeenix @jokeyrhyme