[haiku-development] Re: Support for Firefox in default SetupEnvironment?
- From: "Fredrik Holmqvist" <fredrik.holmqvist@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 7 Mar 2008 16:45:54 +0100
2008/3/7, Stephan Assmus <superstippi@xxxxxx>:
> Hi,
>
> I am wondering about the support of Firefox in our default
> SetupEnvironment. Currently it reads:
>
> export LIBRARY_PATH=
> "%A/lib:$HOME/config/lib:/boot/common/lib:/boot/beos/system/lib"
> export ADDON_PATH=
> "%A/add-ons:$HOME/config/add-ons:/boot/beos/system/add-ons"
>
> We could change that to:
>
> export LIBRARY_PATH=
> "%A/.:%A/components:%A/lib:$HOME/config/lib:/boot/common/lib:/boot/beos
> /system/lib"
> export ADDON_PATH=
> "%A/.:%A/components:%A/add-ons:$HOME/config/add-ons:/boot/beos/system/
> add-ons"
>
> ... in order to support Firefox in "native app" mode. Opinions?
>
> On the other hand, I would have to prepare a package, where the script has
> been removed and firefox-bin renamed to Firefox. In case it works, I might
> as well change the package further and move the components into an
> "add-ons" subfolder. Maybe someone from the BeZilla team could comment on
> that?
>
> Best regards,
>
> -Stephan
Personally I think we shouldn't do this. It may give Haiku a benefit,
but not BeOS or Zeta. So we still have to do work at BeZilla side. The
proper way to do this is to change the packaging for Firefox. We have
a way that so far seems to work, and there are other platforms that do
this.
Only problem is that there is way to much to do and no people. Also
this kind of change should probably happen on trunk, and that means we
need working Cairo and working trunk builds first. We are fighting a
loosing battle unfortunatly. :(
--
Fredrik Holmqvist, TQH
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:
