1. 07 Jun, 2021 3 commits
  2. 02 Jun, 2021 1 commit
  3. 20 May, 2021 6 commits
  4. 19 May, 2021 1 commit
    • Eli Schwartz's avatar
      makepkg: squelch readelf warnings from debug stripping · e176b8ec
      Eli Schwartz authored and Allan McRae's avatar Allan McRae committed
      
      
      readelf --debug-dump sometimes reports inscrutable warnings which don't
      actually affect our extraction of source filenames. For example:
      
      readelf: Warning: There is a hole [0xd3d - 0xd89] in .debug_loc section.
      
      Now gcc 11 seems to have dramatically increased the number of warnings:
      
      readelf: Warning: Corrupt offset (0x0000008e) in range entry 9
      [...]
      readelf: Warning: Corrupt offset (0x000010f0) in range entry 250
      
      The resulting debuginfo created by the very same toolchain works fine,
      as does the list of source filenames. But the warnings are quite
      noisy... send them to /dev/null since they are not actionable in the
      context of getting source files
      Signed-off-by: Eli Schwartz's avatarEli Schwartz <eschwartz@archlinux.org>
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
      e176b8ec
  5. 18 May, 2021 1 commit
  6. 17 May, 2021 3 commits
  7. 09 May, 2021 6 commits
  8. 03 May, 2021 1 commit
  9. 01 May, 2021 7 commits
  10. 23 Apr, 2021 2 commits
  11. 22 Apr, 2021 5 commits
    • Eli Schwartz's avatar
      meson: make our symlinking script more portable · 8fe55207
      Eli Schwartz authored and Allan McRae's avatar Allan McRae committed
      
      
      We do not need the --relative case as it is dead code (we only ever link
      a filename without directory components).
      
      For the rest, GNU-specific ln -T does two things:
      
      - if the link name is an existing directory, ln fails instead of
        creating a surprising link inside the directory
      - if the link name is a symlink to a directory, ln treats it as a file,
        and due to -f, unlinks it
      
      The second case can be portably solved by ln -n, and both cases can be
      solved by doing what the original autotools Makefile did: rm -f && ln -s
      
      If the file exists, it will be removed. If it cannot be removed, it must
      be an ordinary directory, and the script aborts with an error.
      Signed-off-by: Eli Schwartz's avatarEli Schwartz <eschwartz@archlinux.org>
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
      8fe55207
    • Morgan Adamiec's avatar
      Only enable total progress when downloads > 1 · 079b9d44
      Morgan Adamiec authored and Allan McRae's avatar Allan McRae committed
      Otherwise the total progress will just match the one package and be
      pretty useless.
      079b9d44
    • Morgan Adamiec's avatar
      Always enable TotalDownload · 41f9c50a
      Morgan Adamiec authored and Allan McRae's avatar Allan McRae committed
      
      
      Previously TotalDownload would switch the % download from per package to
      overall. Meaning you had a choice of which information to dispplay.
      
      Now with parallel downloads TotalDownload adds an extra progress bar.
      There's no reason to have this an off by default feature. Let's just
      make it always on.
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
      41f9c50a
    • Morgan Adamiec's avatar
      pacman: fix total bar leaking · 63ad8b8b
      Morgan Adamiec authored and Allan McRae's avatar Allan McRae committed
      
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
      63ad8b8b
    • Levente Polyak's avatar
      makepkg: add tool details to buildinfo to aid determining flags · a33cdac1
      Levente Polyak authored and Allan McRae's avatar Allan McRae committed
      
      
      If a makepkg consumer uses a build wrapper to override compiler
      flags this may lead to unreproducible packages as there is no way to
      know which exact files were used for tooling that tries to reproduce
      said package.
      
      Instead of vendoring the whole used makepkg.conf file into buildinfo,
      this patch adds two new properties to the .BUILDINFO file named
      BUILDTOOL and BUILDTOOLVER which by default are simply makepkg's own
      values. Downstream consumers may override those values: For example in
      Arch Linux the devtools package can set those values and allow
      reproducible builds tooling to fetch the appropriate makepkg.conf.
      Signed-off-by: Levente Polyak's avatarLevente Polyak <anthraxx@archlinux.org>
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
      a33cdac1
  12. 21 Apr, 2021 1 commit
  13. 19 Apr, 2021 3 commits