All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] post-build scripts: limitations, and proposal
Date: Sun, 23 Jun 2013 19:06:43 +0200	[thread overview]
Message-ID: <51C72B23.2060105@mind.be> (raw)
In-Reply-To: <CAAXf6LVO6Rz3RXLW++kOOfaHGRvR_4AB8Mi=VS2S-pKhJSm5Lw@mail.gmail.com>

On 21/06/13 08:17, Thomas De Schampheleire wrote:
> Instead of passing multiple scripts, you could just pass one wrapper
> post build script, without options. This wrapper would be different in
> your different configurations, and would call all relevant scripts in
> turn.

  Or alternatively: a wrapper script that observes $0 and decides which 
other scripts to call based on that. So you'd have
rpi-fixup-rootfs at yem@tvheadend for the one configuration, and
rpi-fixup-rootfs at yem@wpa for the other one.

  Regards,
  Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2013-06-23 17:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 21:36 [Buildroot] [RFC] post-build scripts: limitations, and proposal Yann E. MORIN
2013-06-21  6:17 ` Thomas De Schampheleire
2013-06-21  6:59   ` Thomas Petazzoni
2013-06-23 17:06   ` Arnout Vandecappelle [this message]
2013-06-23 17:45     ` Thomas De Schampheleire

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=51C72B23.2060105@mind.be \
    --to=arnout@mind.be \
    --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.