Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gpsd: make init script optional
Date: Sun, 16 Jun 2013 19:37:15 +0200	[thread overview]
Message-ID: <878v2avtx0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAHt8ZCPnR+9SG=rDfyzeLQcbT=UWAwhun4PJ31Ohk=60=0+a7g@mail.gmail.com> (Simon Dawson's message of "Sun, 16 Jun 2013 16:59:06 +0100")

>>>>> "Simon" == Simon Dawson <spdawson@gmail.com> writes:

Hi,

 >> Otherwise, please expand on why not wanting the init script should be
 >> configurable at all.

 Simon> There are other possibilities, beyond SysV and systemd: I've
 Simon> previously run gpsd and other managed services using daemontools
 Simon> and runit.

True, but we don't currently have any support for these in buildroot.

 Simon> My present use case has udev kicking off gpsd in response to
 Simon> hotplug events for a USB GPS device.

 Simon> I seem to always end up having to remove the gpsd SysV init
 Simon> script in my post-build script; hence the desire for a
 Simon> configuration option.

Sorry, but it imho doesn't scale to add configuration options for this
kind of stuff for each package.

Realisticly seem, you almost always need to do some minor fixups in
post-build for any real projects.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2013-06-16 17:37 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 [this message]
2013-06-16 18:16       ` Simon Dawson
2013-06-16 18:30     ` Maxime Ripard
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=878v2avtx0.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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