[haiku-development] Re: Support for Firefox in default SetupEnvironment?
- From: "Fredrik Holmqvist" <fredrik.holmqvist@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 7 Mar 2008 17:47:17 +0100
2008/3/7, Stephan Assmus <superstippi@xxxxxx>:
> What "way" are you referring to? The current Firefox package needs the
> SetupEnvironment change (in UserSetupEnvironment) to work in fully native
> mode. For one thing, I don't understand why Haiku providing it already
> would be negative for the same package on BeOS and ZETA.
>
http://community.livejournal.com/bezilla/255563.html
Even if you add it for Haiku, we need to fix this for BeOS and Zeta as well.
> But re-ordering the package contents doesn't seem like such a huge task to
> me.
No, we just need to prove that it is not breaking things with
netserver, BONE and for other products as Thunderbird, Seamonkey.
After that we need to go thru a lot of red tape to get it into the tree.
This is doable, but it is just not one of the highest priorities for
anyone working right now. I don't even have a proper development
environment right now myself.
>
>
> > Also dynamically loaded libs are loaded with absolute path, so only those
> > linked by firefox-bin directly is needed to launch. OTOH, SSL has a few
> > library checks to make sure it is not compromised, so special care is
> > needed there.
>
>
> So which ones can be moved and which ones can not? You know this better
> than me.
>
> I don't understand what the problem is with writing a script which you can
> use on your setup which does any necessary post-build adjustments to make a
> fully native Firefox package. I know it would be nice to have it in trunk,
> but I don't understand why it is /blocking/ you. Obviously, the problem can
> not be hardcoded paths, since I can put the firefox folder anywhere I like,
> as long as I do so before first starting Firefox.
>
We would need to ship a reordering script separatly, because you can't
call it Firefox otherwise. Hence all those experimental BonEcho
builds. Mozilla is quite strict on how we do things, we only have free
hands in two beos-dirs to
review and commit changes ourselves. As long as we want to release
'Firefox' we can't tamper with the package. If you want reordered
builds you are forced to our 'experimental' BonEcho builds.
--
Fredrik Holmqvist
Chaordic: things that thrive on the edge of chaos with just enough order to
give them pattern, but not so much to slow their adaptation and learning.
Other related posts:
