[sldev] [VWR] llmozlib and xulrunner
Callum Lerwick
seg at haxxed.com
Fri Mar 7 12:04:43 PST 2008
On Fri, 2008-03-07 at 16:37 +0000, Robin Cornelius wrote:
> So for packaging the client for Linux we either have to disable
> llmozlib or ship a full mozilla build. Getting a full mozilla build
> included in Debian or Fedora (Seg can you comment?) just for the sake
> of an embedded browser is a big no no and I cannot see it happening.
Well, it may not be completely impossible to get into Fedora, but it
will need a very convincing argument as to why merging LL's changes
upstream is not possible. It will need to convince me to maintain it,
and to convince the other maintainers to let it in...
One of the major efforts of Fedora 9 has been to integrate xulrunner
across the the entire distribution:
http://fedoraproject.org/wiki/Features/XULRunner
In light of this, adding a mozilla fork would be a step backward.
> Disabling llmozlib is an option, but even thats kind of a pain and
> with things like the whole 1.18.6.X branch it was pretty much a show
> stopper doing such things. With the in world search and all the new
> media things that 1.19.1 brings us not having the embedded browser is
> a bit of a disabling factor.
Yes, in the long run we need this. I believe leveraging the existing web
infrastructure inside SL is the Right Thing to do, but... the current
implementation leaves much to be desired as far as downstream
maintenance is concerned.
> So some questions:-
>
> With all these changes to mozilla, are any of these being submitted to
> the mozilla project to improve the browser in embedded environments?
> so may be one day mozilla xulrunner will do the things we require of
> it?
The first question that will be asked if I bring this up on fedora-devel
will be:
Have the llmozlib developers made every effort to work their changes
upstream?
The answer will have to be yes.
I really can't proceed until I know what the long term intentions are
for llmozlib. Is it a temporary fork until the changes can be worked
upstream, or is LL planning to maintain a fork forever? Is LL even going
to stick with Mozilla, or move to WebKit?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.secondlife.com/pipermail/sldev/attachments/20080307/88641159/attachment.pgp
More information about the SLDev
mailing list