http://forums.gentoo.org/viewtopic.php?p=3787114#3787114
Created attachment 104119 [details] ebuild
I think this is a snapshot not a new release but it's worth having. There are a couple of situations where 9.02 runs 100% cpu.
No official announcement yet, but 9.10 is marked as final on ftp. http://ftp.opera.com/pub/opera/linux/
Created attachment 104248 [details] Ebuild for 9.10 Updated ebuild with support for releases and weekly builds. OPERABUILD is 3rd component of version number OPERADATE is last component (after _p for releases and after _pre for weekly builds) I hope this don't break any ebuild file format rules from http://devmanual.gentoo.org/ebuild-writing/file-format/index.html opera-9.10.521_p20061214.ebuild used as name is for 9.10 release and opera-9.10.518_pre20061212.ebuild for last weekly build
Created attachment 104249 [details] Ebuild for 9.10 Updated ebuild with support for releases and weekly builds. OPERABUILD is 3rd component of version number OPERADATE is last component (after _p for releases and after _pre for weekly builds) I hope this don't break any ebuild file format rules from http://devmanual.gentoo.org/ebuild-writing/file-format/index.html opera-9.10.521_p20061214.ebuild used as name is for 9.10 release and opera-9.10.518_pre20061212.ebuild for last weekly build
Created attachment 104250 [details] Ebuild for 9.10 Updated ebuild with support for releases and weekly builds. OPERABUILD is 3rd component of version number OPERADATE is last component (after _p for releases and after _pre for weekly builds) I hope this don't break any ebuild file format rules from http://devmanual.gentoo.org/ebuild-writing/file-format/index.html opera-9.10.521_p20061214.ebuild used as name is for 9.10 release and opera-9.10.518_pre20061212.ebuild for last weekly build
Sorry for 3 times sending the same patch (Bugzilla freezed 2times during commit and only last one was shown as successfull). Opera announced that build 521 as new weekly build :/ http://my.opera.com/desktopteam/blog/2006/12/14/new-build-available-4 even it's still available here ftp://ftp.opera.com/pub/opera/linux/910/final/en/i386/
(In reply to comment #7) > Opera announced that build 521 as new weekly build :/ > http://my.opera.com/desktopteam/blog/2006/12/14/new-build-available-4 > > even it's still available here > ftp://ftp.opera.com/pub/opera/linux/910/final/en/i386/ Hmm... Not exactly. Take a look at this: http://www.opera.com/download/index.dml?step=2&opsys=Linux%20i386&platform=Linux%20i386 It seems build 521 is the final 9.10. I will try out the proposed ebuild later.
Created attachment 104273 [details] opera-9.10 w. working patching procedure I got this from the previous ebuild: # emerge opera [...] >>> Unpacking opera-9.10-20061214.6-shared-qt.i386-en.tar.bz2 to /var/tmp/portage/www-client/opera-9.10.521_p20061214/work * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /usr/local/portage/www-client/opera/files/opera-9.10-install.patch * ( opera-9.10-install.patch ) !!! ERROR: www-client/opera-9.10.521_p20061214 failed. Call stack: ebuild.sh, line 1580: Called dyn_unpack ebuild.sh, line 716: Called src_unpack opera-9.10.521_p20061214.ebuild, line 78: Called epatch '/usr/local/portage/www-client/opera/files/opera-9.10-install.patch' eutils.eclass, line 198: Called die !!! Cannot find $EPATCH_SOURCE! !!! If you need support, post the topmost build error, and the call stack if relevant. !!! This ebuild is from an overlay: '/usr/local/portage' This attachment should fix it, it only applies the patch if it exists.
(In reply to comment #9) > Created an attachment (id=104273) [edit] > opera-9.10 w. working patching procedure sorry I'm using the same install patch from 9.00 for every weekly build and forget to mention that it's the same with new name. cp /usr/portage/www-client/opera/files/opera-9.00-install.patch /usr/local/portage/www-client/opera/files/opera-9.10-install.patch and new digest should be better patching procedure, than completely ignoring that patch.
I tried the proposed ebuild for 9.10, but it seems to miss the date version from the filename: ebuild opera-9.10.ebuild manifest >>> Creating Manifest for /usr/local/portage/www-client/opera !!! File '/usr/portage/distfiles/opera-9.10-.6-shared-qt.i386-en.tar.bz2' doesn't exist, can't update Manifest
(In reply to comment #11) > ebuild opera-9.10.ebuild manifest of course, ebuild need file name in this form opera-9.10.521_p20061214.ebuild from my first post: opera-9.10.521_p20061214.ebuild used as name is for 9.10 release and opera-9.10.518_pre20061212.ebuild for last weekly build Maybe this way to set parameters by file name instead of in ebuild is bad, but its much simplier for me to copy ebuild to new name than to copy and edit.
(In reply to comment #12) > from my first post: > opera-9.10.521_p20061214.ebuild used as name is for 9.10 release and > opera-9.10.518_pre20061212.ebuild for last weekly build > > Maybe this way to set parameters by file name instead of in ebuild is bad, but > its much simplier for me to copy ebuild to new name than to copy and edit. Thanks, I missed that. :-) The ebuild works fine here.
Odd, before I started using the weeklies I had no trouble with 9.02. Anyhow, current policy says that only official releases make it into the tree, so here we go. Merry Christmas. Ho ho, it's in CVS. I have been using build 521, the-little-weekly-that-could, since December 14th 2006 with no changes to the older official ebuild other than those targeted at accomodating Opera's intricate versioning system, so stabilisation starts on January 18th, 2006 at the earliest (so go find those vulns and speed it up!).
BTW, this should have RESTRICT="strip"; and s/nomirror/mirror/ while at it :)
(In reply to comment #15) > BTW, this should have RESTRICT="strip"; and s/nomirror/mirror/ while at it :) Does this relate to the 9.10 ebuild currently in the tree?
