VectorLinux
October 22, 2014, 05:43:24 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to http://vectorlinux.com/forum1. The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
 
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: 1 2 3 [4] 5 6
  Print  
Author Topic: google chrome linux...  (Read 32506 times)
brokndodge
Member
*
Posts: 83


Linux is sooo HOT


WWW
« Reply #45 on: August 10, 2009, 07:39:13 pm »

well, i switched to vl light on the armada.  found that MOR-lnx was right, i need to test for GConf.  So I updated the code.  Before testing, I decided to remove GConf.  Bad idea.  Half my system is uninstalling right now.  I'm posting my hack while I can, cause I think this is gonna take a reinstall to fix.

0.0.5-untested
Code:
#! /bin/bash
# Title:   install-chrome
# Author:  BroknDodge
# License: BSD
# Version: 0.0.4
#
# Special thanks to the following Vectorians for their help and suggestions:
# Daniel stretchedthin uelsk8ts
# hata_ph rbistolfi MOE-lnx
#
# Very Special thanks to the folks at Chromium.org and Google
# without whom there wouldn't be anything to install
#

#------------------------------------------#
# Setting up the Environment

enablePlugins="$1"
tmp="/tmp"

chromeURL="http://dl.google.com/linux/direct"
chromePackage="google-chrome-unstable_current_i386.deb"

nssURL="http://connie.slackware.com/~alien/slackbuilds/mozilla-nss/pkg/12.2"
nssPackage="mozilla-nss-3.12.3-i486-1alien.tgz"

#------------------------------------------#
# Making sure the system is sane

if [ $UID != 0 ]; then
  echo "You must run this script as root."
  exit 1
fi

if [ -d "$tmp/install-chrome" ]; then # check for and create temp dir
    # Will enter here if dir doesn't exist
    rm -R $tmp/install-chrome # hope you didn't have anything
mkdir $tmp/install-chrome # stored there
else
mkdir $tmp/install-chrome
fi

#------------------------------------------#

function dotests {

echo Running tests...
#------------------------------------------#
# check for lzma

haveLZMA=`which lzma` # check for and getting lzma
if [ "$haveLZMA" == "" ]; then
slapt-get --install lzma
fi

#------------------------------------------#

#------------------------------------------#
# check for nss = 3.12.3

nssInstalled=`slapt-get --search nss-3.12.3` # I really need to check the version
nssInstalled=${nssInstalled#*=} # as well, but this build seems to
nssInstalled=${nssInstalled%]*} # work best with 3.12.3

if [ "$nssInstalled" != "yes" ]; then
installnss
fi
#------------------------------------------#

#------------------------------------------#
# check for nss = 3.12.3

gconfInstalled=`slapt-get --search GConf-2.22.0` # VL-Light doesn't ship with GConf
gconfInstalled=${gconfInstalled#*=}
gconfInstalled=${gconfInstalled%]*}

if [ "$gconfInstalled" != "no" ]; then
slapt-get --install GConf
fi
return
}
#------------------------------------------#


function simlinks {
cd /usr/lib
if [ ! -f "libnspr4.so.0d" ]; then
ln -s libnspr4.so libnspr4.so.0d
fi

if [ ! -f "libnss3.so.1d" ]; then
ln -s libnss3.so libnss3.so.1d
fi

if [ ! -f "libnssutil3.so.1d" ]; then
ln -s libnssutil3.so libnssutil3.so.1d
fi

if [ ! -f "libplc4.so.0d" ]; then
ln -s libplc4.so libplc4.so.0d
fi

if [ ! -f "libplds4.so.0d" ]; then
ln -s libplds4.so libplds4.so.0d
fi

if [ ! -f "libsmime3.so.1d" ]; then
ln -s libsmime3.so libsmime3.so.1d
fi

if [ ! -f "libssl3.so.1d" ]; then
ln -s libssl3.so libssl3.so.1d
fi

return
}

function installnss {

cd $tmp/install-chrome
wget $nssURL/$nssPackage
if [ ! -f "$nssPackage" ]; then
echo "For some reason wget didnt pull nss from Connies"
echo "slackware site"
exit 1
fi
installpkg $nssPackage

rm $nssPackage
return
}

function installchrome {

cd $tmp/install-chrome
wget $chromeURL/$chromePackage

if [ ! -f "$chromePackage" ]; then # quit running if wget failed
echo "Something went wrong while retrieving" # and kick out a sane error msg
echo "Google Chrome"
exit 1
fi

echo "Unpacking the deb file"
ar -x $tmp/install-chrome/$chromePackage

if [ ! -f "data.tar.lzma" ]; then # quit running if ar failed
echo "Something went wrong while unpacking" # and kick out a sane error msg
echo "the .deb file"
exit 1
fi

echo "Extracting Google Chrome"
lzma -d data.tar.lzma
if [ ! -f "data.tar" ]; then # quit running if lzma failed
echo "Something went wrong while extracting" # and kick out a sane error msg
echo "Google Chrome"
exit 1
fi

cd /
echo "Installing Google Chrome"

tar xf $tmp/install-chrome/data.tar
if [ ! -f "/opt/google/chrome/google-chrome" ]; then # let me know if chrome wasn't
echo "Installation failed while" # installed correctly
echo "moving files"
exit 1
fi

if [ "$enablePlugins" = "--enable-plugins" ]; then
IFS='
'
file=( $( < /opt/google/chrome/google-chrome.desktop ) )
file[5]="Exec=/opt/google/chrome/google-chrome --enable-plugins %U"
echo "${file[*]}" > /usr/share/applications/google-chrome.desktop
echo "Desktop Menu created with Plugin support"
echo "Installation complete"
quit
else
cp /opt/google/chrome/google-chrome.desktop /usr/share/applications/google-chrome.desktop
echo "Desktop Menu created without Plugin support"
echo "Installation complete"
echo
echo "to enable flash type google-chrome --enable-plugins"
quit
fi

}

function quit {
exit 0
}

function main {
echo
echo "WARNING WARNING WARNING WARNING WARNING"
echo "This script may severely damage your system"
echo "Dont say I didnt WARN you"
echo
echo "Are you sure you want me to Monkey with your System? [yes/no]"
echo "[for your safety you must type yes to proceed]"
echo
 
read YN
if [ "$YN" = "yes" ]; then
if [ -d "/opt/google/chrome" ]; then
echo "Looks like Google Chrome is already installed"
echo "Do you want to remove it and reinstall? [yes/no]"
read yn
if [ "$yn" = "yes" ]; then
rm -R /opt/google/chrome
rm /usr/share/applications/google-chrome.desktop
dotests
simlinks
installchrome
else
quit
fi
else
dotests
simlinks
installchrome
fi
elif [ "$YN" = "no" ]; then
quit
else
main
fi
quit
}

main
exit
Logged

VL 7.0 Standard

brokndodge
- OSS is not a religion, it's the solution to buggy irresponsible coding -
Linux User# 494720
brokndodge
Member
*
Posts: 83


Linux is sooo HOT


WWW
« Reply #46 on: August 11, 2009, 07:43:11 am »

new version with check for GConf tested, works for me.  MOE-lnx, your right, chrome over vl-light is less than expected.  yet firefox absolutely screems.  it's the other way around on vl-standard. 

now, this GConf issue.  why is it that a packages that isn't installed by default has so many packages that depend on it after it's installed.
Logged

VL 7.0 Standard

brokndodge
- OSS is not a religion, it's the solution to buggy irresponsible coding -
Linux User# 494720
M0E-lnx
Administrator
Vectorian
*****
Posts: 3184



« Reply #47 on: August 11, 2009, 09:19:28 am »

It doesn't have deps on the stock vl-light.
You start running into deps when you extend it Wink

Ideally, the build script would pick up these dependancies and make arrangements to install them on its own. That's what the script is for Wink
Logged

brokndodge
Member
*
Posts: 83


Linux is sooo HOT


WWW
« Reply #48 on: August 11, 2009, 07:16:54 pm »

okay, i think i found out why the buildbot snapshot won't run on my system.  seems it's looking for sse2 support in the processor.  apparently pII doesn't have that.  so when i actually try to build this thing, i'm going to have to find out how to disable that.  i found a conversation on this page close to half way down that talks about this issue:  http://echelog.matzon.dk/logs/browse/chromium/1244152800

seems as if, when you build chromium from source, there is an option somewhere to disable sse2.
Logged

VL 7.0 Standard

brokndodge
- OSS is not a religion, it's the solution to buggy irresponsible coding -
Linux User# 494720
brokndodge
Member
*
Posts: 83


Linux is sooo HOT


WWW
« Reply #49 on: August 11, 2009, 08:46:37 pm »

okay... got the official word from the chromium bug tracking system.  there is a rendering bug in chrome (bug 8475).  they enabled sse2 support in intel p4 and later cpu's to make it go away.  problem is, too many people in the world have amd or p3 or earlier cpu's.  so for the release version, they disable sse2.  that's why chrome works on my pII, but chromium buildbot won't.  so now i have to figure out how to compile with release as my target.

see:
http://code.google.com/p/chromium/issues/detail?id=9007
http://code.google.com/p/chromium/issues/detail?id=8475
« Last Edit: August 11, 2009, 08:57:34 pm by brokndodge » Logged

VL 7.0 Standard

brokndodge
- OSS is not a religion, it's the solution to buggy irresponsible coding -
Linux User# 494720
brokndodge
Member
*
Posts: 83


Linux is sooo HOT


WWW
« Reply #50 on: August 12, 2009, 07:59:01 pm »

at this point, i'm trying to put together a chrome.SlackBuild.  Got enough hacked together that chrome is building on my antique armada right now.  who knows how long that will take.  posting from my wife's windows (UGH) laptop.  the only other machine that wasn't hooked up during that fateful storm.  chrome's build system is, to say the least, awful.  the source package doesn't follow any modern naming conventions and it includes absolutely everything they have for 3 or 4 operating systems.  but, hopefully, i have it worked out well enough to build.  then i just have to figure out the installation stuff. 

so far, my hacks have been to move the chrome stuff to what sbbuilder expects.  the actual build part is custom to chrome.  go figure. they couldn't just do it the linux way.  got to reinvent the wheel.  they use scons and some custom scripts.  this .slackbuild is gonna be ugly, no matter how you look at it. 

if i manage to get a rough package built, will i have to find my own host for it in order to get folks to test it?  figure my first try won't be repo ready.  may take several builds for that.  but i would like to post it somewhere easily accessible.  i also don't want to pollute my filebutler sourceforge page with alien packages. 

any response as to where to post this thing would be greatly appreciated.

thx for all yall's help.
Logged

VL 7.0 Standard

brokndodge
- OSS is not a religion, it's the solution to buggy irresponsible coding -
Linux User# 494720
uelsk8s
Administrator
Vectorian
*****
Posts: 2504



« Reply #51 on: August 12, 2009, 08:23:16 pm »

you can give it to me and I can find somewhere to upload it.
Logged
brokndodge
Member
*
Posts: 83


Linux is sooo HOT


WWW
« Reply #52 on: August 13, 2009, 06:15:58 pm »

thx uelsk8ts, when i get a successful build, i'll let you know.  one of my sons interrupted the build early this morning.  have restarted it.  hopefully it will finish this time.  first deal is to get it to build, then figure out the installation stuff in the SlackBuild.  chrome's build system places everything in $CHROMIUM_ROOT/src/sconsbuilds/Release.  That should result in a file hierarchy identical to the deb file.  so i should just have to mv to the right spot in the sbbuilder folders.  cross my fingers.  got to get a successful build first.  takes over an hour just to extract the src.  who knows how long it will take to build.
Logged

VL 7.0 Standard

brokndodge
- OSS is not a religion, it's the solution to buggy irresponsible coding -
Linux User# 494720
brokndodge
Member
*
Posts: 83


Linux is sooo HOT


WWW
« Reply #53 on: August 16, 2009, 02:27:22 pm »

well, after two and a half days of compiling, the build failed.  error 132 or something like that.  went and got a couple of old hp vectra systems outta storage.  i think i can find enough good ram around here to put together a build system.  will keep trying.

here's what i've got so far (gperf is a required build dep):
Code:

#!/usr/bin/bash
# This script assumes it will be launched within "/NAME/VERSION/src" dir.
# With all sources in "src" Your Vector Linux .tlz package, slack-desc,
# and slack-required will be found in "VERSION" dir. The extraction and
# build will be in a temp dir created in "NAME" dir, and then removed on exit.
# Comment out second to last line to keep this dir intact.
#
# This Template was compiled from the contributions of many users of the Vector
# Linux forum at http://forum.vectorlinux.com and from tidbits collected
# from all over the internet.
#
# Generated by sbbuilder-0.4.12.2, written by Rodrigo Bistolfi
# (rbistolfi) and Raimon Grau Cuscó (Kidd) for VectorLinux.
#
# Please put your name below if you add some original scripting lines.
# AUTHORS = BroknDodge

NAME="chromium"            #Enter package Name!
VERSION=${VERSION:-"r23013"}      #Enter package Version!
VER=$(echo $VERSION|sed 's/-/_/') #this fixes - in version
VL_PACKAGER=${VL_PACKAGER:-"BroknDodge"}   #Enter your Name!
LINK=${LINK:-""}  #Enter URL for package here!
BUILDTOOLS="http://src.chromium.org/svn/trunk/tools/depot_tools.tar.gz"


#SYSTEM VARIABLES
#----------------------------------------------------------------------------
BUILDNUM=${BUILDNUM:-"1"}
VL_VERSION=${VL_VERSION:-"$(ls /var/log/packages/|grep vlconfig2|cut -d "-" -f4|cut -c 2-5)"}
BUILD=${BUILD:-"$BUILDNUM""$VL_VERSION"}
ARCH=${ARCH:-"$(uname -m)"}
CONFIG_OPTIONS=${CONFIG_OPTIONS:-""}
LDFLAG_OPTIONS=${LDFLAG_OPTIONS:-""}
ADDRB=${ADDRB:-""} #Add deps that need to be added to the slack-required file here
EXRB=${EXRB:-""} #Add deps that need to be excluded from the slack-required file here
#----------------------------------------------------------------------------


#SETUP PACKAGING ENVIRONMENT
#--------------------------------------------
CWD=$(pwd)
cd ../
RELEASEDIR=$(pwd)
cd $CWD
mkdir -p $RELEASEDIR/tmp
TMP=$RELEASEDIR/tmp
PKG=$TMP/package-$NAME
CHROMIUM_ROOT=$TMP/home/chrome-svn/tarball/chromium
#--------------------------------------------



if [ $UID != 0 ]; then
   echo "You are not authorized to run this script. Please login as root"
   exit 1
fi

if [ ! -x /usr/bin/requiredbuilder ]; then
   echo "Requiredbuilder not installed, or not executable."
   exit 1
fi

if [ $VL_PACKAGER = "YOURNAME" ]; then
   echo 'Who are you?
   Please edit VL_PACKAGER=${VL_PACKAGER:-YOURNAME} in this script.
   Change the word "YOURNAME" to your VectorLinux packager name.
   You may also export VL_PACKAGER, or call this script with
   VL_PACKAGER="YOUR NAME HERE"'
   exit 1
fi


#CFLAGS SETUP
#--------------------------------------------
if [[ "$ARCH" = i?86 ]]; then
  ARCH=i586
  SLKCFLAGS="-O2 -march=i586 -mtune=i686"
  CONFIGURE_TRIPLET="i486-slackware-linux"
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fpic"
  CONFIGURE_TRIPLET="x86_64-vlocity-linux"
elif [ "$ARCH" = "powerpc" ]; then
  SLKCFLAGS="-O2"
  CONFIGURE_TRIPLET="powerpc-vlocity-linux"
fi

export CFLAGS="$SLKCFLAGS $CFLAG_OPTIONS"
export CXXFLAGS=$CFLAGS
export LDFLAGS="$LDFLAGS $LDFLAG_OPTIONS"
#--------------------------------------------


#GET THE SOURCE
#--------------------------------------------
for SRC in $(echo $LINK);do
if [ ! -f $CWD/$(basename $SRC) ]
then
        wget -c $SRC
fi
done


rm -rf $PKG
mkdir -p $PKG
cd $TMP
rm -rf $NAME-$VERSION


#EXTRACT SOURCES
#-----------------------------------------------------
echo "Extracting source..."
tar xvf $CWD/$NAME.$VERSION.tgz || exit 1
#-----------------------------------------------------


cd $TMP/home

# Put any Patches here
#-----------------------------------------------------
#patch -p1 <
#-----------------------------------------------------


#SET PERMISSIONS
#-----------------------------------------
echo "Setting permissions..."
chown -R root:root .
find . -perm 664 -exec chmod 644 {} \;
find . -perm 777 -exec chmod 755 {} \;
find . -perm 2777 -exec chmod 755 {} \;
find . -perm 775 -exec chmod 755 {} \;
find . -perm 2755 -exec chmod 755 {} \;
find . -perm 774 -exec chmod 644 {} \;
find . -perm 666 -exec chmod 644 {} \;
find . -perm 600 -exec chmod 644 {} \;
find . -perm 444 -exec chmod 644 {} \;
find . -perm 400 -exec chmod 644 {} \;
find . -perm 440 -exec chmod 644 {} \;
find . -perm 511 -exec chmod 755 {} \;
find . -perm 711 -exec chmod 755 {} \;
find . -perm 555 -exec chmod 755 {} \;
#-----------------------------------------

#GET THE BUILD TOOLS
#-----------------------------------------
cd $TMP
wget $BUILDTOOLS
tar xvfz depot_tools.tar.gz
export PATH=$TMP/depot_tools:"$PATH"

#CONFIGURE & MAKE
#----------------------------------------------------------------------
# If you are building a KDE-related app, then change the following
# arguments in the script below:
# --prefix=$(kde-config -prefix) \
# --sysconfdir=/etc/kde \
#
# Making these changes will ensure that your package will build in the
# correct path and that it will work seamlessly within the KDE environment.
#
#-----------------------------------------------------------------------

echo "Configuring source..."
cd $CHROMIUM_ROOT
gclient runhooks --force
cd $CHROMIUM_ROOT/src/build
hammer --implicit-deps-changed --mode=Release chrome
#./configure --prefix=/usr \
#  --sysconfdir=/etc \
#  --localstatedir=/var \
#  --mandir=/usr/man \
#  --with-included-gettext \
#  --disable-debug \
#  --program-prefix="" \
#  --program-suffix="" \
#  --build=$CONFIGURE_TRIPLET \
#  $CONFIG_OPTIONS || exit 1

#make || exit 1

#make install DESTDIR=$PKG || exit

#-----------------------------------------------
# temporary end of script, till i get the build stuff worked out.
exit

#######################################################################
#Miscellenious tweaks and things outside a normal ./configure go here #
#######################################################################



mkdir -p $PKG/usr/doc/$NAME-$VERSION
cp -a AUTHORS COPYING ChangeLog Credits MANIFEST README TODO \
$PKG/usr/doc/$NAME-$VERSION
cat $CWD/$NAME.SlackBuild > $PKG/usr/doc/$NAME-$VERSION/$NAME.SlackBuild

#----------------------------------------------------------------------

if [ -d $PKG/usr/share/man ] ; then
mkdir -p $PKG/usr/man
mv $PKG/usr/share/man/* $PKG/usr/man
rm -rf $PKG/usr/share/man
fi
find $PKG/usr/man -type f -exec gzip -9 {} \;

if [ -d $PKG/usr/share/info ] ; then
mkdir -p $PKG/usr/info
mv $PKG/usr/share/info/* $PKG/usr/info
rm -rf $PKG/usr/share/info
fi

find $PKG/usr/info -type f -exec gzip -9 {} \;
mkdir -p $PKG/install
if [ -d $PKG/usr/info ] ; then
cat >> $PKG/install/doinst.sh << EOF
cd usr/info
if [ -f dir ]; then
    rm dir
fi
if [ -f dir.gz ]; then
    rm dir.gz
fi
for i in *.info.gz
        do
        install-info $i dir
    done
EOF
fi

mkdir -p $PKG/install


#if there is a slack-desc in src dir use it
if test -f $CWD/slack-desc; then
cp $CWD/slack-desc $RELEASEDIR/slack-desc
else
# This creates the white space in front of "handy-ruler" in slack-desc below.

LENGTH=$(expr length "$NAME")
SPACES=0
SHIM=""
until [ "$SPACES" = "$LENGTH" ]; do
SHIM="$SHIM "
let SPACES=$SPACES+1
done

# Fill in the package summary between the () below.
# Then package the description, License, Author and Website.
# There may be no more then 11 $NAME: lines in a valid slack-desc.

cat > $RELEASEDIR/slack-desc << EOF
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description.  Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in.  You must
# make exactly 11 lines for the formatting to be correct.  It's also
# customary to leave one space after the ':'.

$SHIM|-----handy-ruler------------------------------------------------------|
$NAME: $NAME ()
$NAME:
$NAME:
$NAME:
$NAME:
$NAME:
$NAME:
$NAME: License: GPL
$NAME: Authors:
$NAME: Website:

EOF
fi
cat >> $RELEASEDIR/slack-desc << EOF



#----------------------------------------
BUILDDATE: $(date)
PACKAGER:  $VL_PACKAGER
HOST:      $(uname -srm)
DISTRO:    $(cat /etc/vector-version)
CFLAGS:    $CFLAGS
LDFLAGS:   $LDFLAGS
CONFIGURE: $(awk "/\.\/configure\ /" $TMP/$NAME-$VERSION/config.log)

EOF

cat $RELEASEDIR/slack-desc > $PKG/install/slack-desc

#STRIPPING
#------------------------------------------------------------------------------------------------------------------
cd $PKG
echo " "
echo "Stripping...."
echo " "
find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
#------------------------------------------------------------------------------------------------------------------


#FINISH PACKAGE
#--------------------------------------------------------------
echo "Finding dependencies..."
ADD="$ADDRB" EXCLUDE="$EXRB" requiredbuilder -v -y -s $RELEASEDIR $PKG
echo "Creating package $NAME-$VERSION-$ARCH-$BUILD.tlz"
makepkg -l y -c n $RELEASEDIR/$NAME-$VERSION-$ARCH-$BUILD.tlz

cd $CWD
echo "Cleaning up temp files..." && rm -rf $TMP
echo "Package Complete"
#--------------------------------------------------------------

# vim: set tabstop=4 shiftwidth=4 foldmethod=marker : ##
« Last Edit: August 16, 2009, 02:41:43 pm by brokndodge » Logged

VL 7.0 Standard

brokndodge
- OSS is not a religion, it's the solution to buggy irresponsible coding -
Linux User# 494720
Daniel
Packager
Vectorian
****
Posts: 704


WWW
« Reply #54 on: August 16, 2009, 03:36:36 pm »

brokndodge: Just so you know, "chromium" is the name of another package, a game called chromium. And I believe, (from looking at the google-chrome website) that chromium is the name of the project to create google-chrome and google-chrome is the product, the browser.
Logged

The following sentence is true. The previous sentence is false.

VL 6.0 SOHO KDE-Classic on 2.3 Ghz Dual-core AMD with 3 Gigs of RAM
brokndodge
Member
*
Posts: 83


Linux is sooo HOT


WWW
« Reply #55 on: August 17, 2009, 03:44:51 pm »

yup... your right.  the src release and buildbot versions are refered to as chromium. but the release builds,
are refered to as google chrome.  if i can get this thing built, gonna name the final package google-chrome  if google doesn't fuss too much about that.  otherwise, might have to call it chromium.org.  we figure it out then.  right now i can't even get it to build.  so name of the package is kinda splitting hairs.

but thank you for your obversation.  seems like since chromium (the game) has been around so long google should have picked a different name.
Logged

VL 7.0 Standard

brokndodge
- OSS is not a religion, it's the solution to buggy irresponsible coding -
Linux User# 494720
blurymind
Packager
Vectorian
****
Posts: 1082



« Reply #56 on: September 14, 2009, 01:59:06 am »

brokndodge: Just so you know, "chromium" is the name of another package, a game called chromium. And I believe, (from looking at the google-chrome website) that chromium is the name of the project to create google-chrome and google-chrome is the product, the browser.

ubuntu/debian repos call the package chrome-browser or chromium-browser
Logged

status: playing around with new tablet and learning to 3d :p
google page :  http://blurymind.googlepages.com
DA PAGE :  http://www.blurymind.deviantart.com/
stretchedthin
Administrator
Vectorian
*****
Posts: 3780


WWW
« Reply #57 on: September 14, 2009, 08:00:39 am »

Brokndodge has added a script for updating Google-Chrome on his blog.  He is going through a difficult time.  I think I speak for the forum as well when I say we wish him all the best.

I've given this a try and it works very well.

Brokndodges script for updating Google Chrome to latest version.
Logged

Vectorlinux screencasts and  tutorials can be found at....
http://www.opensourcebistro.com/blog1
http://www.youtube.com/user/vid4ken?feature=mhee
brokndodge
Member
*
Posts: 83


Linux is sooo HOT


WWW
« Reply #58 on: September 28, 2009, 07:10:33 pm »

stretchedthin - thank you for your kind words.  i've been absent these last few months  but i haven't forgotten the wonderful folks here in the forum.  i will post a full update on my blog in the next few days and i believe i may be able to begin work on building a vl buildscript for chromium-browser soon.  things are beginning to settle down for me at home, but are beginning to get rather volatile at work.  suffice it to say the president of a 200 million dollar company has my personal cell number at this point.  i'm still not sure if that's good or bad.  i did get one e-mail saying "...i'm impressed." i'm hoping to place myself in a position to promote vl gold.  don't hold your breath... it may all die down soon. 

posting this from a fresh install of vl-gold and google chrome installed from the last posted version of my script.  thx... you guys are great.
Logged

VL 7.0 Standard

brokndodge
- OSS is not a religion, it's the solution to buggy irresponsible coding -
Linux User# 494720
md5fungi
Member
*
Posts: 1


« Reply #59 on: October 10, 2009, 11:54:53 am »

Hey, just a Slackware user that stumbled upon this thread. Downloaded your Google Chrome install script and it works perfectly. Nice work! I know more than a few people that would be interested in this.
Logged
Pages: 1 2 3 [4] 5 6
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!