From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] apache init script
Date: Fri, 2 Mar 2018 21:08:47 +0100 [thread overview]
Message-ID: <20180302210847.48cd8e47@windsurf.home> (raw)
In-Reply-To: <CALURroQSLWQ1TD7gEf-KYqOg3Y8x9mZeo3DAkKd2-B=MZwO02g@mail.gmail.com>
Hello,
On Fri, 2 Mar 2018 09:08:06 -0800, Christopher McCrory wrote:
> I started with the idea of changing just enough of the included init script
> to get the daemon running. I am used to the RedHat/Fedora sysv init
> system, not the debian/start-stop-daemon style. I didn't want to snag some
> other init file using start-stop-daemon, replace a variable, and submit it
> as my own work. I'd rather learn the nuances of start-stop-daemon and
> write a script that I understand and works as expected.
Well, we very much prefer to have init scripts that all follow the same
patterns, rather than init scripts that are all very different from
each other. Having similar init scriptss makes maintenance a lot easier
for us.
So please, re-use the same pattern as existing init scripts. You're not
stealing the work of anyone, because you're also contributing to
Buildroot, under the same license.
> After testing a few other packages, I noticed quite a few that don't have
> init scripts. Is this by design? I'd like to add the ability to generate
> an initscript within the buildroot system. something like
> $PACKAGE_GENERATE_AND_INSTALL_SYSV_INIT_SCRIPT = YES # with a shorter name
> though :)
> in the package.mk file that would use a template to create a working init
> script. And a global toggle in makemenu -> Build Options to
> enable/disable. yes? no? maybe?
Most init scripts have subtle nuances that make a completely
auto-generated init script mechanism not really desirable. I think we
prefer the dumb approach we have today.
However, patches adding init scripts to more packages are definitely
welcome.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-03-02 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 11:50 [Buildroot] [PATCH 2/2] apache init script Christopher McCrory
2018-02-27 21:18 ` Thomas Petazzoni
2018-03-02 17:08 ` Christopher McCrory
2018-03-02 20:08 ` Thomas Petazzoni [this message]
2018-03-01 19:55 ` 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=20180302210847.48cd8e47@windsurf.home \
--to=thomas.petazzoni@bootlin.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