Skip to content
GitLab
Switch branch/tag
  1. 18 Oct, 2019 1 commit
  3. 19 Jul, 2019 1 commit
  5. 18 Jul, 2019 1 commit
  7. 16 Jul, 2019 2 commits
  9. 27 Mar, 2019 7 commits
  11. 07 Sep, 2018 2 commits
  13. 03 Aug, 2018 1 commit
  15. 02 Apr, 2018 6 commits
  17. 27 Feb, 2018 1 commit
  19. 12 Feb, 2018 1 commit
  21. 22 Aug, 2017 1 commit
  23. 06 Aug, 2017 1 commit
  25. 04 Aug, 2017 8 commits
  27. 20 Oct, 2016 1 commit
    • Ian Wienand's avatar
      Show tracing around sourcing environment.d files · 51661c33
      Ian Wienand authored 
      Sourcing of environment files is a bit different than running scripts,
because they are imported into the current environment.  That means
that if they are fiddling with "set -x" you can get odd things in the
output -- for example, if one environment file enables tracing then
all proceeding sourcing will have it on, but all the files sourced
before will not have output.  This is super confusing.

It's also very helpful to see how things are being expanded as they
set environment variables.

Thus I think the best idea is for environment files to leave tracing
alone and dib-run-parts can a) give a useful output about what file it
is sourcing and b) enable tracing around the import, then restore it
to the previous state afterwards.

Change-Id: I29f7df1514aeb988222d1094e8269eddb485c2a0
      51661c33
  29. 03 Jun, 2016 1 commit
  31. 02 Jun, 2016 1 commit
    • Andreas Florath's avatar
      Use 'output' function instead of 'echo' for statistics log · 88497121
      Andreas Florath authored 
      

In bash the only sensible way of returning a string from functions
or scripts is via stdout.
dib-run-parts not only 'returned' the output of the called scripts but
also some statistics / performance output.
Other parts of the script already used an 'output' function so
the statistics output was adapted to also use this kind of function.

In addition three simple test cases are implemented to check
the basic functions of the script.

As a result the log-output of the dib-run-parts is somewhat cleaner.
It also makes debugging of the called scripts easier.
This change is the precondition for simplification of functions like
diskimage-builder's eval_run_d.

Change-Id: Ie2f0332359a72ca7ab03f94b7573e073df714a97
Signed-off-by: default avatarAndreas Florath <andreas@florath.net>
      88497121
  33. 31 May, 2016 1 commit
    • Ian Wienand's avatar
      Source environment files in a subshell · 88097e83
      Ian Wienand authored 
      By sourcing the environment files directly into the running process,
dib-run-parts can pollute its own environment.  For example, if an
environment script enables tracing (set -x) then that enables tracing
for dib-run-parts; particularly annoying as it then spews a bunch of
stuff relating to the profiling.

Move to sourcing the environment files in a subshell with the scripts
to be executed to keep things separate.

Change-Id: I1e39822f218dc0322e2490a770f3dc867a55802c
      88097e83
  35. 19 May, 2016 2 commits
  37. 28 Feb, 2016 1 commit