aurutils: aur-build should not require -f for VCS packages

From aur-build(1) in aurutils-2.0.1-1:

  -f, --force
         Continue the build process if a package with the same name is
         found (ignoring the extension). Existing packages will be moved
         with a ~ suffix.

Unfortunately the check if a package with the same name is found seems to be done before the pkgver() function of VCS packages is executed, which is very un-makepkg-like.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 1
  • Comments: 21 (17 by maintainers)

Commits related to this issue

Most upvoted comments

As I understand it, the issue is that aur-vercmp-devel is an all-or-nothing deal. This makes me think any non-trivial parts should be moved elsewhere, and the process better documented, since it’s clearly not a 1-size-fits-all solution.

633cb12f38b8753a18758f7b902df8f7b2e2a527

Thanks for the report!

On Sat, 12 Jan 2019 05:44:23 -0800 Jakub Klinkovský notifications@github.com wrote:

I have devtools (required for aur-chroot anyway) so I’m fine with 1.

– You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/AladW/aurutils/issues/500#issuecomment-453748681

– Alad Wenter alad@archlinux.org