* [Buildroot] providing post-build scripts in buildroot [not found] <1890922777.231675.1362739947331.JavaMail.root@openwide.fr> @ 2013-03-08 10:55 ` Jeremy Rosen 2013-03-08 10:58 ` Thomas Petazzoni 0 siblings, 1 reply; 5+ messages in thread From: Jeremy Rosen @ 2013-03-08 10:55 UTC (permalink / raw) To: buildroot 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] providing post-build scripts in buildroot 2013-03-08 10:55 ` [Buildroot] providing post-build scripts in buildroot Jeremy Rosen @ 2013-03-08 10:58 ` Thomas Petazzoni 2013-03-08 11:30 ` Jeremy Rosen 0 siblings, 1 reply; 5+ messages in thread From: Thomas Petazzoni @ 2013-03-08 10:58 UTC (permalink / raw) To: buildroot Dear Jeremy Rosen, On Fri, 8 Mar 2013 11:55:39 +0100 (CET), Jeremy Rosen wrote: > 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) I don't have a strong opinion on this, but doesn't this belongs to the documentation instead? Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] providing post-build scripts in buildroot 2013-03-08 10:58 ` Thomas Petazzoni @ 2013-03-08 11:30 ` Jeremy Rosen 2013-03-08 12:12 ` Thomas Petazzoni 0 siblings, 1 reply; 5+ messages in thread From: Jeremy Rosen @ 2013-03-08 11:30 UTC (permalink / raw) To: buildroot > > I don't have a strong opinion on this, but doesn't this belongs to > the > documentation instead? > i'm not sure what you mean here... do you want the script mentionned in the documentation ? in that case yes, that makes sense do you want the script "directly included as text" in the doc ? I am less convinced, unless you want to use them as examples rather than tools provided by the poject.... ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] providing post-build scripts in buildroot 2013-03-08 11:30 ` Jeremy Rosen @ 2013-03-08 12:12 ` Thomas Petazzoni 2013-03-08 13:21 ` Jeremy Rosen 0 siblings, 1 reply; 5+ messages in thread From: Thomas Petazzoni @ 2013-03-08 12:12 UTC (permalink / raw) To: buildroot Dear Jeremy Rosen, On Fri, 8 Mar 2013 12:30:13 +0100 (CET), Jeremy Rosen wrote: > i'm not sure what you mean here... do you want the script mentionned > in the documentation ? in that case yes, that makes sense > > do you want the script "directly included as text" in the doc ? > I am less convinced, unless you want to use them as examples rather > than tools provided by the poject.... Yes, the scripts included directly into the documentation. At the last Buildroot meeting, we've discussed the idea of extending the documentation with more "Use cases descriptions", i.e how to use Buildroot in practice for a project. I think examples of what can be done in post-build scripts who fit quite well in this. Best regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] providing post-build scripts in buildroot 2013-03-08 12:12 ` Thomas Petazzoni @ 2013-03-08 13:21 ` Jeremy Rosen 0 siblings, 0 replies; 5+ messages in thread From: Jeremy Rosen @ 2013-03-08 13:21 UTC (permalink / raw) To: buildroot > Yes, the scripts included directly into the documentation. At the > last > Buildroot meeting, we've discussed the idea of extending the > documentation with more "Use cases descriptions", i.e how to use > Buildroot in practice for a project. I think examples of what can be > done in post-build scripts who fit quite well in this. > ok, thx i'll get my scripts into an upstreamable shape and include them in the documentation ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-03-08 13:21 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1890922777.231675.1362739947331.JavaMail.root@openwide.fr>
2013-03-08 10:55 ` [Buildroot] providing post-build scripts in buildroot Jeremy Rosen
2013-03-08 10:58 ` Thomas Petazzoni
2013-03-08 11:30 ` Jeremy Rosen
2013-03-08 12:12 ` Thomas Petazzoni
2013-03-08 13:21 ` Jeremy Rosen
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox