From: Alex Suykov <alex.suykov@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v2 0/5] common service startup files
Date: Mon, 6 Apr 2015 01:01:19 +0300 [thread overview]
Message-ID: <cover.1428263859.git.alex.suykov@gmail.com> (raw)
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.
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.
---
v2 changes: this part of the v1 series is now standalone, the script
got simplified a lot, and it now requires explicit variables instead
of just picking up files from the package directory.
Run files format reverted to "key: value" with explicit keys.
It is still somewhat custom, and the script is still in python however.
Non-daemon script support dropped completely, and some rare complex
cases like postgres dropped as well.
Hard-coded paths removed, TARGET_DIR is used when appropriate.
Variable substitution and special cases are now handled in package
makefiles, not in the script.
--
2.0.3
next reply other threads:[~2015-04-05 22:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-05 22:01 Alex Suykov [this message]
2015-04-05 22:01 ` [Buildroot] [RFC v2 1/6] common service startup files Alex Suykov
2015-04-05 22:02 ` [Buildroot] [RFC v2 2/6] squid: common service startup Alex Suykov
2015-04-05 22:02 ` [Buildroot] [RFC v2 3/6] dropbear: " Alex Suykov
2015-04-05 22:03 ` [Buildroot] [RFC v2 4/6] samba4: " Alex Suykov
2015-04-05 22:04 ` [Buildroot] [RFC v2 5/6] gpsd: " Alex Suykov
2015-04-05 22:04 ` [Buildroot] [RFC v2 6/6] acpid: " Alex Suykov
2015-04-06 8:51 ` [Buildroot] [RFC v2 0/5] common service startup files Thomas Petazzoni
2015-04-21 22:00 ` Yann E. MORIN
2015-04-22 12:44 ` Mike Williams
2015-04-22 21:11 ` Thomas Petazzoni
2015-04-22 22:02 ` Alex Suykov
2015-04-22 22:28 ` Arnout Vandecappelle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1428263859.git.alex.suykov@gmail.com \
--to=alex.suykov@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox