RFC common init infrastructure
Get series with b4
b4 am 20150322132358.GC21403@vostroVersions newest first
- v1 RFC Latest0 of 11 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 11 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Buildroot] [RFC 00/11] common init infrastructure
Quoted 5 lines · Yann E. MORIN
How do you handle conditional creation of users/groups? Let's take a supposed package that can install a server and/or a client (like a SQL related package, for example). The server (sqld) needs a specific user+group, but the client (sql-cli) does not. Currently, this is easily done by emclosing the user defintion between a 'if server' block.
I think it makes sense to install users unconditionally.
Mostly because not installing them is a minor optimization of the resulting rootfs image and I see no good way to handle it.
If necessary, perhaps listing .users to be included in the project .mk file may be an option, the same way it is done with .run files.
Quoted 4 lines
Otherwise, I have a feeling this is pushing things a bit too far. I'm usually very happy with "abstraction" and I more than once have pushed for such changes. However, in this area, I'm a bit sceptic as to whether we should introduce our own "initscript" format (the '.run' files).
That's a valid point, but I think buildroot already uses its own initscript format, namely its sysv(-style) initscripts.
They are supplied with buildroot, they are non-standard, and they are nearly useless outside of buildroot.
So I see it a choice between different formats for buildroot-specific service description, and the one currently in use does not look like a good data storage format at all.