[semi-solved]chromium-browser-bin

Question

Hi,
I had to do a full system upgrade today and when I came to the point where I wanted to install my favourite browser, yaourt failed.
I typed:
$yaourt -S chromium-browser-bin
A list of the usual stuff pops up, eg. the comments and what not.. Then I get the typical warning about whether or not I would like to modify the pkgbuild which, of course, I would select yes (problem still happens if I hit no).. Immediately after that, I'm back with
chromium-browser-bin LATEST-12 : The open-source project behind Google Chrome
( Unsupported package: Potentally dangerous ! )
==> Edit the PKGBUILD (highly recommended for security reasons) ? [Y/n]("A" to abort)
==> ----------------------------------------------
==>n
[molecular-bio@archbox ~]$
Does this potentially mean that this package is deleted?
yaourt works for other packages, so I'm not sure here... I really, really liked the chromium-browser-bin package.
Thank you
Last edited by 10wattmindtrip (2009-12-28 14:18:01)

Answer 1

The problem is with yaourt's parser.  Using a different AUR helper, this problem disappears.
However, I can understand the attraction of using Yaourt.  You can make chromium-browser-bin and chromium-codecs-ffmpeg-nonfree-bin work with yaourt by editing the PKGBUILDs.  Where it says:
case "$CARCH" in
i686|i[3-5]86) _bldarch='chromium-rel-linux';;
x86_64|amd64) _bldarch='chromium-rel-linux-64';;
# The following should not happen; provided you're using 'makepkg' ;)
*) error "Unknown or invalid CARCH=$CARCH"; exit 1
esac
Replace that with the one for the version that you have:
64-bit Arch
_bldarch=chromium-rel-linux-64
32-bit Arch
_bldarch=chromium-rel-linux
(Edit: stupidly had the two swapped)
Last edited by airbreather (2010-03-17 12:25:03)