View previous topic :: View next topic |
Author |
Message |
bigjohn Guru
Joined: 30 Nov 2003 Posts: 317 Location: 5100N, 0019W
|
Posted: Thu Mar 24, 2005 8:58 pm Post subject: Opera 8 beta 3 |
|
|
I noticed yesterday that opera 8 beta 3 is now available from the opera site in a "gentooised" format.
Having downloaded it, how would I actually get it installed so that it upgrades the beta_2 version that I've got installed, and so that portage doesn't complain (I already have the beta_2 installed after having put the "various bit" in the /etc/portage/package.keywords and listed it in /etc/portage/package.unmask).
Sorry if that sounds like a lame question, but I'll be blowed if I can find the answer (which, yes, is probably in front of my nose!).
Cheers
John _________________ How to read manpages
rute users handbook
Take care with "emerge -U" |
|
Back to top |
|
|
RuiP l33t
Joined: 15 Jan 2005 Posts: 643
|
Posted: Thu Mar 24, 2005 10:00 pm Post subject: |
|
|
I download it too, thinking it was an ebuild... it's just a normal tar.gz with a install script.
If you wanna try, i think you should first unemerge your beta2, and then just ./install.sh on the dir where you uncompressed the downloaded file.
anyway it should go to portage soon... maybe the better way was just wait a couple of days
(another way is just edit the ebuild ) _________________ ESTRAGON: We've lost our rights?
VLADIMIR: (distinctly) We got rid of them. |
|
Back to top |
|
|
pseudonym n00b
Joined: 23 Mar 2005 Posts: 5
|
Posted: Fri Mar 25, 2005 1:17 pm Post subject: |
|
|
I created the ebuild myself, by editing the beta2 ebuild.
Download these three files, and copy to the appropriate places:
/usr/portage/www-client/opera/
/usr/portage/www-client/opera/
/usr/portage/www-client/opera/files/
Then
Code: | ACCEPT_KEYWORDS="~x86" emerge -a opera |
Should do it!
If you emerge --sync, the files you addedd will be deleted (or maybe replaced with the official ebuild, when it's made).
Here's what I did for those interested (not sure if it's right!)
Code: | cd /usr/portage/www-client/opera/
cp opera-8.00_beta2.ebuild opera-8.00_beta3.ebuild
nano -w opera-8.00_beta3.ebuild
# change these lines: OPERAVER="8.0-20050316"
# OPERAFTPDIR="800b3/beta/en"
# save
# This downloads the opera binarys from ftp.opera.com, md5sums them, and stores the result -- it's used when emerging "md5 src_uri ;-)" and so on
ebuild /usr/portage/www-client/opera/opera-8.00_beta3.ebuild digest |
Now to try out the SVG... |
|
Back to top |
|
|
Maedhros Bodhisattva
Joined: 14 Apr 2004 Posts: 5511 Location: Durham, UK
|
Posted: Fri Mar 25, 2005 1:20 pm Post subject: |
|
|
Moved from Desktop Environments. _________________ No-one's more important than the earthworm. |
|
Back to top |
|
|
bigjohn Guru
Joined: 30 Nov 2003 Posts: 317 Location: 5100N, 0019W
|
Posted: Sat Mar 26, 2005 11:40 pm Post subject: |
|
|
pseudonym wrote: | I created the ebuild myself, by editing the beta2 ebuild.
Download these three files, and copy to the appropriate places:
/usr/portage/www-client/opera/
/usr/portage/www-client/opera/
/usr/portage/www-client/opera/files/
Then
Code: | ACCEPT_KEYWORDS="~x86" emerge -a opera |
Should do it!
If you emerge --sync, the files you addedd will be deleted (or maybe replaced with the official ebuild, when it's made).
Here's what I did for those interested (not sure if it's right!)
Code: | cd /usr/portage/www-client/opera/
cp opera-8.00_beta2.ebuild opera-8.00_beta3.ebuild
nano -w opera-8.00_beta3.ebuild
# change these lines: OPERAVER="8.0-20050316"
# OPERAFTPDIR="800b3/beta/en"
# save
# This downloads the opera binarys from ftp.opera.com, md5sums them, and stores the result -- it's used when emerging "md5 src_uri ;-)" and so on
ebuild /usr/portage/www-client/opera/opera-8.00_beta3.ebuild digest |
Now to try out the SVG... |
Oh dear, that's all just a little bit over my head. Bugger!
I suppose I'll have to wait and get it when it appears!
Thanks anyway.
regards
John _________________ How to read manpages
rute users handbook
Take care with "emerge -U" |
|
Back to top |
|
|
javac16 Tux's lil' helper
Joined: 10 Aug 2003 Posts: 111
|
Posted: Sat Mar 26, 2005 11:48 pm Post subject: |
|
|
Thanks - I had done a similar thing with the ebuild, but used your Manifest and digest files.
You may want to use the PORTAGE OVERLAY so the ebuild, etc. don't get erased on sync.
/etc/make.conf
Code: |
PORTDIR_OVERLAY="/usr/local/portage"
|
Code: |
mkdir -p /usr/local/portage/www-client/opera/files
|
Copy the Manifest and ebuild into /usr/local/portage/www-client/opera/
Copy the digest file into /usr/local/portage/www-client/opera/files
Modify your package.unmask and package.keywords files:
Code: |
echo "=www-client/opera-8.00_beta3 ~x86" >> /etc/portage/package.keywords
echo "=www-client/opera-8.00_beta3" >> /etc/portage/package.unmask
|
|
|
Back to top |
|
|
pseudonym n00b
Joined: 23 Mar 2005 Posts: 5
|
Posted: Sun Mar 27, 2005 12:17 am Post subject: |
|
|
javac16 wrote: | Thanks - I had done a similar thing with the ebuild, but used your Manifest and digest files.
You may want to use the PORTAGE OVERLAY so the ebuild, etc. don't get erased on sync. |
Ah, that's excellent -- thanks
So to bigjohn:
Code: |
# Add a second, local, portage tree in /usr/local/portage
echo 'PORTDIR_OVERLAY="/usr/local/portage"' >> /etc/make.conf
# Make a folder for Opera in this tree
mkdir -p /usr/local/portage/www-client/opera/files
# Download the Opera ebuild into the local tree:
cd /usr/local/portage/www-client/opera/files
wget http://matt.blissett.me.uk/2005/03/gentoo_opera_8.00_beta3/digest-opera-8.00_beta3
cd ..
wget http://matt.blissett.me.uk/2005/03/gentoo_opera_8.00_beta3/opera-8.00_beta3.ebuild
wget http://matt.blissett.me.uk/2005/03/gentoo_opera_8.00_beta3/Manifest
# This will allow portage to use the unstable beta version (without it, you'd still get 7.54 final)
echo "=www-client/opera-8.00_beta3 ~x86" >> /etc/portage/package.keywords
echo "=www-client/opera-8.00_beta3" >> /etc/portage/package.unmask
# And emerge!
emerge -a opera |
Should install beta 3. |
|
Back to top |
|
|
Gentree Watchman
Joined: 01 Jul 2003 Posts: 5350 Location: France, Old Europe
|
Posted: Fri Apr 15, 2005 11:03 am Post subject: |
|
|
Quote: | Copy the Manifest and ebuild into /usr/local/portage/www-client/opera/
Copy the digest file into /usr/local/portage/www-client/opera/files |
I dont see the sence is copying this stuff just let ebuild and portage do its job.
cd to you overlay directory containing the beta3 ebuild then:
ebuild *beta3* digest
emerge opera _________________ Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86 |
|
Back to top |
|
|
Archangel1 Veteran
Joined: 21 Apr 2004 Posts: 1212 Location: Work
|
Posted: Sat Apr 16, 2005 10:59 am Post subject: |
|
|
Gentree wrote: | I dont see the sence is copying this stuff just let ebuild and portage do its job. |
It's conceptually quite different - if you use pseudonym's method Portage downloads the tarball and verifies it's md5 hash against the digest file you've got. This ensures that the tarball is the one the guy who made the ebuild was expecting you to use, so it's not corrupted in any way.
There's a significant security thing too - the ebuild doesn't have any malicious code inserted into it. Your way, someone could potentially man-in-the-middle you and send you whatever they wanted, and once you've got it you tell Portage it's okay.
It's not really a big deal; I doubt anything along those lines has ever happened, but it is possible. There is a reason emerge sync copies all those digest files down to your machine...
Obviously you still have to trust the guy that wrote the ebuild script and digest in the first place, but that kind of goes without saying... _________________ What are you, stupid? |
|
Back to top |
|
|
Gentree Watchman
Joined: 01 Jul 2003 Posts: 5350 Location: France, Old Europe
|
Posted: Sat Apr 16, 2005 6:33 pm Post subject: |
|
|
Of course its conceptually different , that's why I suggested doing it directly.
First off , rsync is not done over a secure connection so the whole my portage three could be full of your men-in-the-middle.
Accepting that I can trust my portage tree, the safest way to get opera-beta3 is to tweek the beta2 ebuild to the newer location at opera.com and get the files and the md5 checksum from there in the normal way. From the horses mouth as it were.
I hardly see it as a securty advantage grabbing a load of files of some totally unknown noob-geek's home server in his bedroom and blindly taking it on trust. (No offense to the person hosting the files I'm just making the point to archange1)
Especially when I wget a whole directory which could contain anything and an ebuild that I will execute with root privilages without spending the time to go through what it does with a fine tooth comb.
Now if you could explain again the serious security point and how it is safer than trusting the gentoo mirrors and opera.com and how rsync more prone to a man-in -the-middle attack than wget. I seem to have missed the crux of your security policy.
Thx.
BTW I am told that opera8 final is out but my check for update in opera says I have the latest version. beta3==final ? _________________ Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86 |
|
Back to top |
|
|
Taladar Guru
Joined: 09 Oct 2004 Posts: 458 Location: Bielefeld, Germany
|
|
Back to top |
|
|
Gentree Watchman
Joined: 01 Jul 2003 Posts: 5350 Location: France, Old Europe
|
Posted: Tue Apr 19, 2005 6:43 pm Post subject: |
|
|
OK , looks like they finally caught up with thier own "final" . It now on the main page:
http://www.opera.com/
Thanks for your posts. _________________ Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86 |
|
Back to top |
|
|
|