[haiku-development] Re: Support for Firefox in default SetupEnvironment?

Fredrik Holmqvist wrote:
> 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

Thank you very much for this link! Going to test right now! :-)

> Even if you add it 
> for Haiku, we need to fix this for BeOS and Zeta as well.

We already have an R5, BONE and ZETA package. Personally, I wouldn't mind a 
Haiku package which is different from the rest. This is only temporarily 
anyways, until we have all happily switched to Haiku fully. ;-)

> > 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.

The Haiku package needs to work well on Haiku only.

> 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.

Consider this a testbed for what exactly needs to be done and how. The more 
exposure this setup gets, the better you know what to change in trunk... :-)

> >  > 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.

Yes, the naming is a problem, I can see that. If it has to be called "Bon 
Echo" for the time being, so be it.

Best regards,
-Stephan

Other related posts: