Package Details: packer-git v1.4.3_177_g39a57af3e-1

Git Clone URL: https://aur.archlinux.org/packer-git.git (read-only, click to copy)
Package Base: packer-git
Description: Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
Upstream URL: https://www.packer.io/
Licenses: MPL2
Conflicts: packer
Provides: packer
Submitter: dg10a
Maintainer: None
Last Packager: dg10a
Votes: 4
Popularity: 0.000000
First Submitted: 2019-09-17 01:50 (UTC)
Last Updated: 2019-09-17 01:50 (UTC)

Dependencies (3)

Required by (5)

Sources (1)

Latest Comments

dg10a commented on 2019-07-07 18:55 (UTC)

Packer is in community now: https://www.archlinux.org/packages/community/x86_64/packer/

Could you change the binary path, conflicts, and package name to "packer" to match?

wezm commented on 2017-07-30 00:28 (UTC)

The esx5_HostKeyCallback.patch is no longer required as it's on master now https://github.com/hashicorp/packer/blob/master/builder/vmware/iso/driver_esx5.go#L395

zosodk69 commented on 2017-05-19 23:20 (UTC)

Sorry about that. It looks like packer was moved: https://github.com/hashicorp/packer/commit/81522dced0b25084a824e79efda02483b12dc7cd

y2kbadbug commented on 2016-05-02 21:02 (UTC)

I flagged the package out of date as it appears the package has not been updated in almost a year and is currently broken.

kamazee commented on 2014-09-17 02:44 (UTC)

Looks like it also needs bzr for some reason: imports github.com/going/toolkit/xmlpath: exec: "bzr": executable file not found in $PATH With bzr added as make dependency it builds fine.

howardad commented on 2014-08-01 13:04 (UTC)

Looking at it again this morning, I'm not quite sure why I made some of those choices. I definitely agree with your comment about prepare(), there is no reason at all to remove it. Some of the changes I made were in response to build errors I got, but it looks like the real problem I had was adding typos in paths ($srcdir/com.github... instead of $srcdir/src/com.github... etc). Anyway, thanks for adding the one useful line!

zosodk69 commented on 2014-08-01 04:02 (UTC)

Good catch. It's a good idea to remove the existing build directory. I've added an rm to prepare(). Your PKGBUILD seems to have a lot of added noise to accomplish this small task. Is there a reason you removed prepare()? It's my understanding that the reason we have separate prepare and build functions is so that we can makepkg -o to make modifications by hand, then run makepkg -e to build with our modifications.

howardad commented on 2014-08-01 02:53 (UTC)

I was having trouble getting this to work correctly with pacaur after the first build (main problem was the mv in prepare() when not building from a completely clean directory), so I made a few changes to the PKGBUILD. If you want to incorporate them, they are at https://gist.github.com/howardad/dc1b58361f58c0b8e9a3