I've created an ebuild for Firefox 1.1 Alpha 1 (also known as "Deer Park Alpha 1" .. actually the browser doesn't call itself Firefox at all, but it is). I haven't tested the non-bin version due to bandwidth reasons (dialup, don't want to wait for the 40MB source package to download). But the -bin package looks like it's downloading. And it's pretty much a hackjob since the real 1.1 will be placed into firefox/1.1 rather than firefox/deerpark/alpha1. I could have mucked about with the ${MY_PV} but I didn't feel like it Reproducible: Always Steps to Reproduce:
Created attachment 61086 [details] www-client/mozilla-firefox-bin-1.1_pre1.ebuild
Created attachment 61087 [details] www-client/mozilla-firefox-1.1_pre1.ebuild
this bug shoud depends on bugs #69654 #70820 for internalization.
Created attachment 62800 [details] www-client/mozilla-firefox-1.1_pre1.ebuild with fixed SRC_URI Looks like mozilla.org/ changed the directory just a bit on us, fixed.
Well, actually trying the source package ebuild it's afu, epatches are still in (and probably shouldn't be until it's verified they're still needed) and without them the configure fails with: checking MOZ_GTK2_LIBS... -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 configure: error: Cannot enable XFT and FREETYPE2 at the same time. A simple digging through the ebuild comes up with nothing too useful.
>www-client/mozilla-firefox-1.1_pre1.ebuild with fixed SRC_URI text/plain 2005-07-06 12:59 PDT It's use patches for 1.0.4 and can't apply it to 1.1: * Failed Patch: mozilla-firefox-1.0-4ft2.patch ! * ( /usr/local/portage/www-client/mozilla-firefox/files/mozilla-firefox-1.0- 4ft2.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/mozilla-firefox-1.1_pre1/temp/mozilla-firefox-1.0-4ft2. patch-2620.out !!! ERROR: www-client/mozilla-firefox-1.1_pre1 failed. !!! Function epatch, Line 359, Exitcode 0 !!! Failed Patch: mozilla-firefox-1.0-4ft2.patch! !!! If you need support, post the topmost build error, NOT this status message.
USE=moznoxft emerge mozilla-firefox
Can someone make an ebuild for the latest (1.5 beta1), or will renaming these ebuilds work? Can we make one bug be the official bug for getting/discussing beta ebuilds ..i don't think these will ever be put into portage, so at least I can just put them in my ebuild overlays directory.
I would like to use firefox 1.5 beta as well. Although I dont understand why it wont ever be put into portage. I used beta firefox long before 1.0 came out and those were in portage.
I have already put the source ebuilds in the tree they are keyword masked. I have no plans on adding binary release canadiates, someone else on mozilla team might. I will bring it up in next discussion as to weather or not we will add them.
Maybe closing time as there now is a mozilla-firefox-bin-1.5 in portage?
1.5 final is in the tree.
