From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 02/11] ejabberd: simplify init script by patching ejabberdctl
Date: Sun, 19 Jul 2015 23:09:43 +0200 [thread overview]
Message-ID: <20150719230943.1f63c757@free-electrons.com> (raw)
In-Reply-To: <CAJtjsKZeXXQvGimN=Zq1gdPLSwX5LY1J=Jh0J9L8SYwBK6y9XQ@mail.gmail.com>
Johan,
On Tue, 14 Jul 2015 11:52:41 +0200, Johan Oudinet wrote:
> > So this makes the patch Buildroot specific. Why isn't the
> > {{installuser}} properly replaced by the "right" value at install time?
>
> If we define the installuser variable, then the Makefile try to chmod
> files with this user, which does not necessarily exist in the host
> system. Debian packaging of ejabberd does the same trick to not set
> the installuser variable and patch the ejabberdctl instead. In the
> last buildroot version of ejabberd, each call of ejabberdctl was
> prefixed by "su ejabberd -c", which is less convenient than fixing
> INSTALLUSER to ejabberd.
> If you prefer, I could modify this variable in a post-build hook.
Ok, thanks for the additional explanation. The proposal you made works
for me, especially since Debian is doing the same.
> > I don't really understand why we are loading this default file here and
> > in the init script itself. Who is installing this /etc/default/ejabberd
> > file? What does it contain?
>
> I like shell scripts that read a configuration files in /etc/default
> so one can modify the script behavior without modifying it.
Me too. What was confusing me is that both the init script *and* the
ejabberdctl script were reading it. But you gave some good explanation
for that.
> > This change doesn't seem to be related.
>
> Which one? Using $CTL instead of ctl because we removed the ctl
> function or try to start the service even if stop failed?
> I agree that the second one is not related to the simplification of
> the init script. Should I split it in another commit?
The change to start the service even if the stop failed. But that's
a minor detail.
Therefore, I've applied the patch as is. Thanks again for this
contribution and the additional explanations!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-19 21:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 9:54 [Buildroot] [PATCH 00/11] Bump ejabberd version to 15.06 Johan Oudinet
2015-07-08 9:54 ` [Buildroot] [PATCH 01/11] ejabberd: bump to version 15.06 Johan Oudinet
2015-07-08 9:54 ` [Buildroot] [PATCH 02/11] ejabberd: simplify init script by patching ejabberdctl Johan Oudinet
2015-07-11 10:30 ` Thomas Petazzoni
2015-07-14 9:52 ` Johan Oudinet
2015-07-19 21:09 ` Thomas Petazzoni [this message]
2015-07-08 9:54 ` [Buildroot] [PATCH 03/11] ejabberd: fix package version Johan Oudinet
2015-07-11 10:31 ` Thomas Petazzoni
2015-07-14 10:02 ` Johan Oudinet
2015-07-08 9:54 ` [Buildroot] [PATCH 04/11] erlang-p1-utils: bump to version 1bf99f9 Johan Oudinet
2015-07-08 9:54 ` [Buildroot] [PATCH 05/11] erlang-p1-cache-tab: bump to version f7ea12b Johan Oudinet
2015-07-08 9:54 ` [Buildroot] [PATCH 06/11] erlang-p1-tls: bump to version b070004 Johan Oudinet
2015-07-08 9:54 ` [Buildroot] [PATCH 07/11] erlang-p1-stringprep: bump to version 3c64023 Johan Oudinet
2015-07-08 9:54 ` [Buildroot] [PATCH 08/11] erlang-p1-xml: bump to version 2c61083 Johan Oudinet
2015-07-08 9:54 ` [Buildroot] [PATCH 09/11] erlang-p1-stun: bump to version a3dce07 Johan Oudinet
2015-07-08 9:54 ` [Buildroot] [PATCH 10/11] erlang-p1-sip: bump to version fd3e461 Johan Oudinet
2015-07-08 9:54 ` [Buildroot] [PATCH 11/11] erlang-p1-yaml: bump to version e1f081e Johan Oudinet
2015-07-11 10:28 ` [Buildroot] [PATCH 00/11] Bump ejabberd version to 15.06 Thomas Petazzoni
2015-07-14 9:10 ` Johan Oudinet
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=20150719230943.1f63c757@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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