From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxime Ripard Date: Sun, 16 Jun 2013 20:30:51 +0200 Subject: [Buildroot] [PATCH] gpsd: make init script optional In-Reply-To: References: <1371382468-5838-1-git-send-email-spdawson@gmail.com> <20130616130904.GD3495@free.fr> Message-ID: <20130616183051.GZ16699@lukather> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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 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