amend 6365e14f

Fixes #735

This ensures that all built packages were moved to the local repository
before moving them. In particular, if an error occurs before the move,
the built package is not lost.

This was done after some concern that PKGDEST may be used by other
programs (in particular, build systems) besides makepkg. However, the
variable is defined in makepkg(8) as being possible part of the
environment, and the custom makepkg.conf parser has broken before (i.e.
a newline was missing in the last concatenated makepkg.conf file).

As this problematic mostly arised due to yaourt exporting every variable
in makepkg.conf (BUILDDIR included), restore the original behavior. See
also:

https://wiki.archlinux.org/index.php?title=Talk:AUR_helpers&oldid=590741#Drop_%22Clean_Build%22_Column

The [multilib] assumption is only valid on x86_64 systems. (Issue #722)

One-line variant of linking build files:

xargs -a "$tmp"/queue -d'\n' realpath -z | xargs -0 ln -t "$tmp_view" -s --

--log was added as workaround when makepkg output went "missing" while
using paralell. Since we no longer use parallel (and --log
apparently stacks the logs, potentially resulting in dozens of log
files), remove the option again.

Rafael Ascensão authored 5 years ago and Alad Wenter committed 4 years ago

The aur-jobs wrapper does little more than remove the citation nagging,
which was since removed by upstream packager[1], thus we can retire
aur-jobs.

[1]:https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/parallel&id=e2abd3a81e6848bc18993ed878ba45ec4f39ef9d

Alad Wenter authored 5 years ago and Alad Wenter committed 4 years ago

See #582. This commit also adds the `-j`/`--jobs` flag for the upper bound of makepkg jobs.

Co-Authored-By: rafasc <rafa.almas@gmail.com>

Fixes #732

Rafael Ascensão authored 5 years ago and Alad Wenter committed 5 years ago

We tried to teach aur-chroot long option parsing in commits:
    * b9d33917 (aur-chroot: fix #462, 2018-12-01)
    * 98fe97bb (aur-chroot: add long options, 2018-12-01)
But failed to mark options that *require* arguments appropriately.

Fix #637

Alad Wenter authored 6 years ago and Alad Wenter committed 5 years ago

Removed in pacman.

https://git.archlinux.org/pacman.git/commit/?id=9adb0d5b37df7ca668e23877e85431dabeea005e

Fixes #547

Rafael Ascensão authored 6 years ago and Alad Wenter committed 6 years ago

`aur sync` will use $PAGER if `vifm` is not avaiable, falling back to
`less -K` if $PAGER is unset. `aur sync` uses the exit code from this
invocation to decide if the build process should continue or should be
aborted. This is a important part of the process as continuing implies
the user reviewed and agreed to run the PKGBUILD.

While vifm and the current default (less -K) allows exiting with error
by using :cq or ^C respectively, if the user has $PAGER set to something
that doesn't wait for user input and provide a way to exit with error,
or has LESS=F which causes `less` to exit successfully if the output
fits in one page, aur sync will proceed without explicitly consent from
the user.

Let's override the -F option on our default fallback making sure it
always paginate, and prompt for confirmation whenever a custom $PAGER is
set in order to always have explicit consent from the user and a way to
abort if desired.

Fixes #530

James Alad Bork authored 6 years ago and Alad Wenter committed 6 years ago

As suggested by https://github.com/AladW/aurutils/commit/634a60a73bbe84ca8b797a7b3a4e7ff23cae3869#r32415966

#455

#217

+sort alphabetically

#350

Closes #437

Closes #437

Closes #507

Closes #438