From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] apache init script
Date: Tue, 27 Feb 2018 22:18:15 +0100 [thread overview]
Message-ID: <20180227221815.21afde38@windsurf.lan> (raw)
In-Reply-To: <20180227115022.8802-1-chrismcc@gmail.com>
Hello,
Thanks for this contribution!
The commit title should be something like:
apache: install an sysv init script
On Tue, 27 Feb 2018 03:50:22 -0800, Christopher McCrory wrote:
> This patches and installs the included init script. The script mostly works, but could use a little more editing.
The commit log should be wrapped to 72 characters.
> package/apache/0003-init-script.patch | 56 +++++++++++++++++++++++++++++++++++
> package/apache/apache.mk | 6 ++++
> 2 files changed, 62 insertions(+)
> create mode 100644 package/apache/0003-init-script.patch
>
> diff --git a/package/apache/0003-init-script.patch b/package/apache/0003-init-script.patch
> new file mode 100644
> index 0000000000..1d7a6a022a
> --- /dev/null
> +++ b/package/apache/0003-init-script.patch
All patches should have a description and a Signed-off-by line.
What does the complete init script looks like after your patch ? Is it
worth re-using the init script provided by Apache, as opposed to
providing a simple one in package/apache/S<xy>apache ?
> +define APACHE_INSTALL_INIT_SCRIPT
Just call this variable:
APACHE_INSTALL_INIT_SYSV
This way, no need to add it to APACHE_POST_INSTALL_TARGET_HOOKS, and
the script will not be installed if the Buildroot configuration uses
systemd instead of busybox init or sysvinit.
> + $(INSTALL) -D -m 0755 $(@D)/build/rpm/httpd.init \
> + $(TARGET_DIR)/etc/init.d/S85httpd
Second line should be intended with two tabs.
> +endef
> +APACHE_POST_INSTALL_TARGET_HOOKS += APACHE_INSTALL_INIT_SCRIPT
So this line can go away.
Could you take into account those comments and submit an updated
version ?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-27 21:18 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 [this message]
2018-03-02 17:08 ` Christopher McCrory
2018-03-02 20:08 ` Thomas Petazzoni
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=20180227221815.21afde38@windsurf.lan \
--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