Package Details: iron-bin 42.0.2250.1-1

Package Base: iron-bin
Description: A web browser based on Chromium without Google's «tracking features»
Upstream URL: http://www.srware.net/en/software_srware_iron.php
Category: network
Licenses: BSD
Submitter: None
Maintainer: triceratops1
Last Packager: Jristz
Votes: 1
First Submitted: 2015-03-22 15:43
Last Updated: 2015-05-29 03:25

Latest Comments

Comment by LeonardK

2015-06-10 15:21

@gim
> Why would someone upload this scamware to AUR again?

Because everyone believes that if they state "OSS" it is. Sure, this browser is closed-source, completely intransparent and totally useless (Chromium+ any AdBlocker serves it's function well enough), but not everybody knows...

Comment by Jristz

2015-05-29 03:34

I tried, but look like the i686 is so old and buggy, if someone want they can try fix the rendering problem

Comment by gim

2015-04-11 21:05

Why would someone upload this scamware to AUR again?

Comment by ChickTower

2015-04-11 02:59

Well, I tried modifying PKGBUILD to use the src/iron-linux-64 directory that the "correct" source tarball creates. makepkg completed, seemingly successfully, except it complained that strip couldn't work on iron, libffmpegsumo.so, libpdf.so, and chrome_sandbox. It said they had an unrecognized file format, or something akin to that. It finished, I installed it, but Iron v.40 refuses to run. So I'm back to v.37.

I did notice on the SRWare website that they no longer make a 32-bit build of Iron. I had assumed that, since this PKGBUILD compiles the source, that wouldn't matter, but maybe there is something in the source that prevents it from running on 32-bit PCs and v.37 is the last one that will.

In short, this PKGBUILD does not work on 32-bit Manjaro Linux, and for at least two reasons. I am unable to test whether it works on 32-bit Arch or any 64-bit Linux.

Comment by ChickTower

2015-04-10 23:24

I tried building iron-bin on a 32-bit laptop running Manjaro Linux. I know it's not Arch, but they both use the AUR. I downloaded the tarball, uncompressed it, and ran makepkg in the resulting directory. It downloaded a different source file than specified on this webpage and in the .SRCINFO. It was called iron-linux.tar.gz, not iron-linux-64.tar.gz. Since it was a different file, if failed the validity check.

So I downloaded iron-linux-64.tar.gz and put it in the iron-bin directory in place of iron-linux.tar.gz. I ran makepkg again, and this time it passed the validity check, but it failed because the PKGBUILD expected a different directory than was created. If I recall correctly, an src/iron-linux-64 was created, but the PKGBUILD was looking for src/iron-linux.

What I finally did was replace the "wrong" file the PKGBUILD downloaded and run makepkg without the validity checks. I, too, got the error about not having convert installed, but I thought that could be because I was using Manjaro. After installing imagemagick, it compiled, but I just now noticed I have version 37, not 40, of Iron. Just great. Maybe I'll modify things myself to successfully compile the iron-linux-64 version of the source, if I can.

Comment by liepumartins

2015-04-10 09:15

PKGBUILD: line 64: convert: command not found

Probably should add imagemagick as build dep.

Comment by sl1pkn07

2015-03-31 17:42

please update launcher for handle a separate pepperflash (and possible other plugins) config file.

https://bugs.archlinux.org/task/43804