RFC common service startup files
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 RFC Latest posting 2/20 of 5 patches 0 repliesNew
- v2 RFC posting 1/20 of 5 patches 0 repliesSuperseded
Patches in v2 posting 2/2 No applies recorded yet
None of the 5 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [Buildroot] [RFC v2 0/5] common service startup files
Dear Alex Suykov,
Quoted 18 lines · Alex Suykov
This series is intended to simplify and clean up installation routine for daemon-like applications, merging sysv and systemd startup files and moving much of the common code out of per-package .mk files.
Currently buildroot requires pre-crafted sysv and/or systemd startup files to be supplied for each package that needs its daemon-like processes started at system boot. In many cases, this is redundant.
Only a small part of the startup scripts is package-specific. A single command, the one that starts the process in foreground mode, is typically enough to generate usable sysv and systemd startup files.
Separating package-specific data and removing the rest from package directories allows changing common code without the need to patch several dozen packages, ensures more or less even support for sysv and systemd, and potentially simplifies introduction of alternative system startup schemes.
Quoted 4 lines
The first patch in the series contains the common code, and the rest show how it affects individual packages. I'm only posting a few interesting ones with comments; the full set (~50 patches) is available
here: https://github.com/arsv/br/ branch run-1.
Thanks for this proposal. However, as you have seen, the general feedback was not very positive. We don't really like having a specialized language being created for Buildroot, so the overall approach doesn't really match the "spirit" of how things are done in Buildroot.
I've marked the corresponding patches as rejected in our patch tracking system.
Thanks for your contribution!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com