Package Details: bastion-hib 1.2+h20161016-1

Git Clone URL: https://aur.archlinux.org/bastion-hib.git (read-only, click to copy)
Package Base: bastion-hib
Description: An action role-playing game set in a lush imaginative world (Humble Bundle/Store version)
Upstream URL: http://www.supergiantgames.com/games/bastion/
Keywords: 3D action ARPG combat game humble post-apocalyptic role-playing RPG top-down
Licenses: custom
Groups: hib5, hib9
Conflicts: bastion
Replaces: bastion
Submitter: smls
Maintainer: smls
Last Packager: smls
Votes: 28
Popularity: 0.000000
First Submitted: 2015-07-28 21:44 (UTC)
Last Updated: 2016-11-04 12:13 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 11 Next › Last »

ejona86 commented on 2012-06-20 06:26 (UTC)

In hopes that it won't get missed, it seems the pkgver should be 20120613. I mentioned that the issue that we had with yaourt was not a yaourt issue. Instead, it was those of us using symbolic links to refer to the Bastion-HIB .sh script. The PKGBUILD simply has a bug when Bastion-HIB-2012-06-13.sh is a symbolic link. This affects manually building with makepkg. The fix I chose was simply to replace "-type f" with "-maxdepth 1" when _archive is being set via a find. The only difference yaourt makes with regard to your PKGBUILD is that echos don't show up; PKGBUILD has ways other than echo to print messages, and it doesn't seem too bad to change to using them (since then you specify if they are info, warning, error). Note that I don't care too much about this, I was just saying FYI. As a note, "yaourt -G" sources the PKGBUILD after it runs sanitize_pkgbuild() on it (so it may not be safe either). Yaourt uses makepkg for the package building. I just looked at cower and it doesn't look like it supports different dependencies for x86 vs amd64. Maybe I read the source wrong. If you are on the subject of verifying packages are non-malicious before running them, then the _humblebundle function actually makes that quite difficult.

gtmanfred commented on 2012-06-20 02:45 (UTC)

ok, I am not going to add support for yaourt to auto build it, it is not a supported by archlinux, So I have no desire to support it if they are going to break the pkgbuilds by sanatizing them first and then sourcing, none of that stuff needs to be done by yaourt, go complain to them. on the note about _humblebundle() not working. use yaourt -G , get the tar ball and just run makepkg -si ... it isn't that hard. in the next update of pacman, I will be able to include SKIP in the md5sum array then everything in the _humblebundle function can be moved to build(), but until then just stick with the default and use yaourt -G or better yet switch to cower, an aur helper that gets the tarball and untars it for you and doesn't do any of the work that makepkg is designed to do... It also doesn't source the PKGBUILD before you can read it like yaourt and packer and pacaur and meat and owl all do. thats right, the security that you think you have because it offers you the opportunity to read the PKGBUILD before they run it is moot, get package, makepkg PKGBUILD that has depends=("$(rm -rf $HOME)") your home directory will be gone before you can read the pkgbuild

ejona86 commented on 2012-06-20 02:11 (UTC)

Shouldn't pkgver be 20120613? PostBlue: Yeah, I had problems with yaourt too, but it turned out not to be yaourt's fault. It was likely because you used a symbolic link like I did. The _humblebundle function was quite painful when using a symbolic link for the .sh file. The find used to set _archive specified "-type f", which doesn't detect symbolic links. I was forced to replace that part with "-maxdepth 1" and then everything started working. It was quite painful to debug that though. Also, I will note that echo's aren't displayed using yaourt.

postblue commented on 2012-06-15 13:15 (UTC)

The "_humblebundle" line at the end of the file make the file impossible to read for yaourt.

<deleted-account> commented on 2012-06-15 09:34 (UTC)

Thanks gtmanfred, it works for me now. makepkg gives some warnings about the package containing references to $pkgbuild, but the package tar seems ok.

CPUnltd commented on 2012-06-15 07:07 (UTC)

sorry for the double post... refreshed the page. Tried bastionmesa and the imagery was there, but it's currently moving sluggish (on a 6-core system with 32GB of ram), so I'm not sure what the deal is. Couldn't get past the initial screen that says "press any key"... Something else might be choking my system though... will reboot and try again tomorrow.

gtmanfred commented on 2012-06-15 05:22 (UTC)

@CPUnltd did you try bastionmesa? like it said in the .install file

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 11 Next › Last »