1. 14 Mar, 2016 1 commit
  2. 11 Feb, 2016 3 commits
    • anonym's avatar
      Move gettext initialization code to the top of shell scripts. · 0be0def5
      anonym authored
      That's what we do in most places, so let's be consistent.
      0be0def5
    • anonym's avatar
      Avoid set -u issue when testing if variable is set or not. · 364a3c8d
      anonym authored
      Whenever there's a risk that we will reference a shell variable in a
      script run with `set -u` (including libraries that we sources from
      such scripts) we must reference the variable in a way so it gets a
      default value, i.e. `${VAR:-}` to give it the empty string as the
      default (which is what generally makes sense).
      
      In particular, it's quite clear that in all cases where we do
      something like `[ -n "${VAR}" ]` or `[ -z "${VAR}" ]`, where an
      expected value is the empty string, which could mean that the variable
      is not initialized, we should give such a default (as the empty
      string).
      364a3c8d
    • anonym's avatar
      Add set -u to all gettext:ized shell scripts. · 74a91c28
      anonym authored
      In gettext-base < 1.8.2, like the one we had in Wheezy, gettext.sh
      references the environment variable ZSH_VERSION, which we do not
      set. This has prevented us from doing `set -u` in all gettext:ized
      shell scripts unless we first initialize that variable before sourcing
      gettext.sh.
      
      Now that we install a new enough gettext-base, we can finally do this
      and remove the initialization hacks.
      
      Will-fix: #9371
      74a91c28
  3. 18 Nov, 2015 1 commit
  4. 11 Nov, 2015 1 commit
  5. 16 Feb, 2015 1 commit
  6. 14 Jan, 2015 1 commit
  7. 30 Nov, 2014 2 commits
  8. 29 Nov, 2014 1 commit
  9. 28 Nov, 2014 6 commits
  10. 21 Oct, 2014 16 commits
  11. 20 Oct, 2014 7 commits