From: Nathan Ford <nford@westpond.com>
To: buildroot@busybox.net
Subject: [Buildroot] init script installation policy
Date: Wed, 02 Apr 2014 09:54:41 -0400 [thread overview]
Message-ID: <533C16A1.3080508@westpond.com> (raw)
What is the policy for installing init scripts when there is already an
init script in the target location? Currently there does not seem to be
any consistency. I bring this up as I updated a project to a newer
buildroot recently and a package I use went from not installing the init
script if it was present, to always installing.
For my projects I use a custom skeleton fs and like the fact that I can
just store my custom init scripts for the packages I use in the skeleton.
Thanks,
--Nate
next reply other threads:[~2014-04-02 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 13:54 Nathan Ford [this message]
2014-04-02 15:55 ` [Buildroot] init script installation policy Thomas De Schampheleire
2014-04-03 6:10 ` 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=533C16A1.3080508@westpond.com \
--to=nford@westpond.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.