From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] providing post-build scripts in buildroot
Date: Fri, 8 Mar 2013 11:55:39 +0100 (CET) [thread overview]
Message-ID: <1825560181.231790.1362740139485.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <1890922777.231675.1362739947331.JavaMail.root@openwide.fr>
Hello everybody
I am currently creating a couple of post-build scripts for my own personal use that could
be usefull for the general audience...
* copy the local id_ras.pub to the target
* generate the host key of the target during build time
* copy the target's host key to the known_host of the user
Since post-build is a new feature I was wondering if the project was opened to distributing that
sort of scripts somewhere in the support directory ( something like support/post-build)
Cordialement
J?r?my Rosen
fight key loggers : write some perl using vim
next parent reply other threads:[~2013-03-08 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1890922777.231675.1362739947331.JavaMail.root@openwide.fr>
2013-03-08 10:55 ` Jeremy Rosen [this message]
2013-03-08 10:58 ` [Buildroot] providing post-build scripts in buildroot Thomas Petazzoni
2013-03-08 11:30 ` Jeremy Rosen
2013-03-08 12:12 ` Thomas Petazzoni
2013-03-08 13:21 ` Jeremy Rosen
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=1825560181.231790.1362740139485.JavaMail.root@openwide.fr \
--to=jeremy.rosen@openwide.fr \
--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