I get some errors when emerging (see below). But it works anyway. I think we can add it as masked. An error occurred reading the startup configuration file. Please contact your administrator. line 47: ReferenceError: defaultPref is not defined. An error occurred reading the startup configuration file. Please contact your administrator. line 40: ReferenceError: config is not defined. An error occurred reading the startup configuration file. Please contact your administrator. line 47: ReferenceError: defaultPref is not defined. An error occurred reading the startup configuration file. Please contact your administrator. line 40: ReferenceError: config is not defined.
Problem with anything masked, is that it always gets merged, and there will be complaints to mailing lists, or even bug reports. I vote to wait for a more stable alpha, or better yet, beta release.
Mozilla 1.1a works fine for me. I don't think it's very unstable. Anyway, isn't the sense of masked packages to add bleeding-edge packages that aren't stable enough?
*** Bug 5065 has been marked as a duplicate of this bug. ***
Only 1 prob with this ebuild... It should be called mozilla-1.1_alpha.ebuild otherwise Portage will consider mozilla-1.1.ebuild (which I assume will be the release version) a lower version then mozilla-1.1a.ebuild.
New Mozilla is out. 1.1 beta. I have stuck an ebuild into Portage for it however it is not guarenteed to work and I am the one supporting it... not Azarah. However support will be very minimal since it is a beta release.
