1. 11 May, 2019 1 commit
  2. 26 Apr, 2019 3 commits
  3. 19 Apr, 2019 3 commits
  4. 12 Apr, 2019 3 commits
  5. 06 Apr, 2019 2 commits
  6. 11 Mar, 2019 3 commits
  7. 06 Mar, 2019 1 commit
  8. 05 Mar, 2019 4 commits
  9. 20 Dec, 2018 3 commits
  10. 15 Dec, 2018 3 commits
  11. 11 Dec, 2018 2 commits
  12. 08 Dec, 2018 1 commit
    • Andreas Henriksson's avatar
      Pass more paths explicitly to configure · d1c705f9
      Andreas Henriksson authored
      These paths are otherwise looked up from PATH at build-time
      and embedded into shipped files. This means that for example
      on merge-usr systems tools are found in /usr/bin that on
      non-merged systems live in /bin.
      
      When building in a local dirty environment, they could of
      course be picked up from any other place also in PATH, like
      /usr/local/bin.
      
      The additions in this commit fixes only the part of the reproducability
      problem related to merged-usr vs non-merged systems (but the package
      still doesn't build reproducably in general) and it only caters
      for the paths affected by merged-usr.... There might still be
      other paths that should also be specified explicitly that could
      be affected for other reasons than merged-usr in a local dirty
      build environment.
      d1c705f9
  13. 02 Jul, 2018 3 commits
  14. 28 Jun, 2018 3 commits
  15. 16 Jun, 2018 1 commit
  16. 31 May, 2018 2 commits
  17. 30 May, 2018 1 commit
  18. 23 Apr, 2018 1 commit