Arch Linux User Repository

Updated to version 1.2+h20161016. Humble Bundle unfortunately does not provide change logs, so I'm not sure if anything changed about the game itself or if they only released this update because they switched to the MojoSetup installer. ImageMagick is now a build dependency because for some reason they now bundle the icon as a BMP file, which is not a valid icon format according to the freedesktop.org specification <https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html>, so I let the package convert it to PNG.

Adopted for AUR4.

In gtmanfred's defense, I have seen zero documentation of the hib:// download method. Perhaps if the wiki page for non-free apps [1] was updated with more info about custom dlagents, or if a page was created for HIB game packaging guidelines, switching would make more sense. Maybe? My point is, although using hib:// for HIB games is consistent, some guidelines should be written down.

I'd also like an updated PKGBUILD with hib:// method, so that HIB packages are consistent.

did you even check what the .sh installer did? because I have... the answer is still now, unless it is broken or needs to be updated versions, it isn't changing right now

"just requiring the source tarball be included as well" Yes, that is pretty much what I meant - except that instead of calling the source-array entry "Bastion-HIB-${_pkgver}.sh", you would call it "hib://Bastion-HIB-${_pkgver}.sh". The hib prefix won't make a difference for users who don't have a hib:// dlagent set up, as makepkg will always look for files in the PKGBUILD folder first regardless of the protocol/path prefix. But for users who do have a corresponding dlagent set up, it will make it much more convenient. I still keep a DLAGENTS+=(...) line in my hib PKGBUILDs, but only to print an informational message as a courtesy to new users. "I am not using hib-dlagent" Neither am I, instead I have a bash one-liner dlagent defined in makepkg.conf, that makes it look for game archives in ~/downloads and subdirectories: DLAGENTS=( ... 'hib::/usr/bin/find /home/sam/downloads -name $(echo %u | cut -c 7-) -exec ln -s \{\} %o \; -quit') That's the beauty of using the hib:// protocol: Every user can set up whatever system they prefer - or just continue to manually symlink game archives to their PKGBUILD folders. "as for not extracting it, if you check the sh, it has a --packager pacman." That doesn't mean that the installer reliably always does the same thing, in fact if previous experiences with hib installers are anything to go by it wont, because it probably tries to be "smart" and reacts to which libraries are currently installed on the system etc. Also I've seen hib installers have annoying side-effects like putting .desktop files in the home directory of the user who runs it, and stuff like that. All in all, it's just a dirty/unsafe way to extract it.

I am not using hib-dlagent, in fact I have been thinking about just removing the whole dlagent thing and just requiring the source tarball be included as well. as for not extracting it, if you check the sh, it has a --packager pacman. and the finally for force extracting, there is no need, because again, the have options for setting everything to be installed into the $pkgdir.

This game is now also in Humble Bundle 9! So, a good time to clean up / modernize the PKGBUILD I'd say :) Now that 'hib-dlagent' exists, it no longer makes any sense to implement HIB downloading inside PKGBUILD's. Simply use: source=("hib://Bastion-HIB-${_pkgver}.sh" ... ) It will make the PKGBUILD a *lot* shorter and easier to read, and will greatly increase convenience because users are by now used to Humble Bundle AUR packages doing this way, and most will have already set up a hib dlagent of their choice in makepkg.conf Another thing that should be improved is the way the archive is extracted - executing the installer is bad (because of potential side-effects/unreliability), and I'm pretty sure the archive can be force-extracted directly (at least I remember succeeding in doing so in PKGBUILDs for other HIB games that used a similar installer; I'd have to investigate). PS: If you no longer have an active interest in the game and don't want to deal with maintaining/improving the package anymore, just disown it - I'd gladly take over... :P

@cookiecaper: The DLAGENTS=(...) has an error, the fix was described below - replace: /usr/bin/curl -sL --cookie /tmp/cjar --cookie-jar /tmp/cjar --data "username=$_humbleemail" --data "password=$_humblepassword" %u with /usr/bin/curl -sL --cookie /tmp/cjar --cookie-jar /tmp/cjar -F "username=$_humbleemail" -F "password=$_humblepassword" %u

I get this when the Bastion upgrade tries to run. $ makepkg -fis ==> Making package: bastion 20120621-7 (Thu Jul 11 09:18:05 MDT 2013) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Downloading Bastion-HIB-2012-06-20.sh... curl: (3) <url> malformed -> Downloading Bastion-HIB-2012-06-20.sh... curl: no URL specified! curl: try 'curl --help' or 'curl --manual' for more information ==> ERROR: Failure while downloading Bastion-HIB-2012-06-20.sh