Re: usage of basu as requirement for sd-bus

2022-08-30 Thread Maxime Devos
On 30-08-2022 11:27, muradm wrote: IIUC, everything using basu also works fine with elogind (*), so the 'status quo' of still using elogind (for old and new) seems harmless to me (except for size -- basu is smaller). I don't find the "everything using basu also works fine with elogind"

Re: usage of basu as requirement for sd-bus

2022-08-30 Thread muradm
Maxime Devos writes: [[PGP Signed Part:Undecided]] On 30-08-2022 09:59, muradm wrote: Hello, basu is sd-bus library extracted from systemd. Currently, there are two packages depending on it, which are mako and grimshot. In https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56859, I suggest

Re: usage of basu as requirement for sd-bus

2022-08-30 Thread Maxime Devos
(**) This is just a guess about what your goal was, maybe you had a different reason in mind. E.g., basu seems to be more active than elogind. Oops I misread the dates -- the latest commit in basu was before the latest commit in elogind. OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP

Re: usage of basu as requirement for sd-bus

2022-08-30 Thread Maxime Devos
On 30-08-2022 09:59, muradm wrote: Hello, basu is sd-bus library extracted from systemd. Currently, there are two packages depending on it, which are mako and grimshot. In https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56859, I suggest switching xdg-desktop-portal-wlr to basu. In very same

usage of basu as requirement for sd-bus

2022-08-30 Thread muradm
Hello, basu is sd-bus library extracted from systemd. Currently, there are two packages depending on it, which are mako and grimshot. In https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56859, I suggest switching xdg-desktop-portal-wlr to basu. In very same issue, Maxime asks to discuss