From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gpsd: make init script optional
Date: Sun, 16 Jun 2013 20:30:51 +0200 [thread overview]
Message-ID: <20130616183051.GZ16699@lukather> (raw)
In-Reply-To: <CAHt8ZCPnR+9SG=rDfyzeLQcbT=UWAwhun4PJ31Ohk=60=0+a7g@mail.gmail.com>
On Sun, Jun 16, 2013 at 04:59:06PM +0100, Simon Dawson wrote:
> Hi Yann, Maxime.
>
> On 16 June 2013 14:09, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > Why would one not want the init script? Is this because of systemd? If so,
> > then you should use GPSD_INSTALL_INIT_SYSV and GPSD_INSTALL_INIT_SYSTEMD
> > as pointed out by Maxime.
> >
> > This ensures the init script will only be installed if a SysV init
> > scheme is used (and conversely for the systemd unit).
> >
> > Otherwise, please expand on why not wanting the init script should be
> > configurable at all.
>
> There are other possibilities, beyond SysV and systemd: I've
> previously run gpsd and other managed services using daemontools and
> runit. My present use case has udev kicking off gpsd in response to
> hotplug events for a USB GPS device.
>
> I seem to always end up having to remove the gpsd SysV init script in
> my post-build script; hence the desire for a configuration option.
Maybe you can add a BR2_INIT_NONE choice here then to not copy all the
install scripts.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-06-16 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 11:34 [Buildroot] [PATCH] gpsd: make init script optional spdawson at gmail.com
2013-06-16 12:34 ` Maxime Ripard
2013-06-16 13:09 ` Yann E. MORIN
2013-06-16 15:59 ` Simon Dawson
2013-06-16 17:37 ` Peter Korsgaard
2013-06-16 18:16 ` Simon Dawson
2013-06-16 18:30 ` Maxime Ripard [this message]
2013-06-18 6:24 ` Arnout Vandecappelle
2013-06-18 7:07 ` Thomas Petazzoni
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=20130616183051.GZ16699@lukather \
--to=maxime.ripard@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