Re: [systemd-devel] [RFC] xyzctl-common

2013-12-02 Thread Lennart Poettering
On Sat, 16.11.13 19:41, Peeters Simon (peeters.si...@gmail.com) wrote: > hello all, > > During the sd_bus porting I noted that the *ctl tools (and > systemd-analyze) contain a lot of common boilerplate code. > > So the basic idea is to split this boilerplate out into > xyzctl-common.[ch] so that

Re: [systemd-devel] [RFC] xyzctl-common

2013-11-16 Thread Peeters Simon
2013/11/16 Zbigniew Jędrzejewski-Szmek : > On Sat, Nov 16, 2013 at 07:41:13PM +0100, Peeters Simon wrote: >> hello all, >> >> During the sd_bus porting I noted that the *ctl tools (and >> systemd-analyze) contain a lot of common boilerplate code. >> >> So the basic idea is to split this boilerplate

Re: [systemd-devel] [RFC] xyzctl-common

2013-11-16 Thread Zbigniew Jędrzejewski-Szmek
On Sat, Nov 16, 2013 at 07:41:13PM +0100, Peeters Simon wrote: > hello all, > > During the sd_bus porting I noted that the *ctl tools (and > systemd-analyze) contain a lot of common boilerplate code. > > So the basic idea is to split this boilerplate out into > xyzctl-common.[ch] so that f.ex the

[systemd-devel] [RFC] xyzctl-common

2013-11-16 Thread Peeters Simon
hello all, During the sd_bus porting I noted that the *ctl tools (and systemd-analyze) contain a lot of common boilerplate code. So the basic idea is to split this boilerplate out into xyzctl-common.[ch] so that f.ex the bottom hostnamectl.c would look like: ... static void help(void ) {...} en