Main inclusion for Google Gadgets

Bug #314778 reported by Jonathan Riddell
28
This bug affects 3 people
Affects Status Importance Assigned to Milestone
google-gadgets (Ubuntu)
Won't Fix
Undecided
Unassigned
Revision history for this message
Alexander Sack (asac) wrote :

-xul package lacks binary depends on xulrunner-1.9.

fwiw, how essential is the -xul support? It uses its own glue wrapper to load and use mozjs (which is better than directly linking against mozjs using -rpath) ... mozjs however has no api policy and putting this in main might cause issues on xulrunner sec updates.

Maybe we can disable -xul part of the build or simply not ship that bin package in main until mozjs devs have come up with a policy?

Changed in google-gadgets:
status: New → Incomplete
Revision history for this message
Alexander Sack (asac) wrote :

... also not sure about one part of copyright:

third_party/xdgmime/*.h:
third_party/xdgmime/*.c:
        Copyright (C) 2003,2004 Red Hat, Inc.
        Copyright (C) 2003,2004 Jonathan Blandford <email address hidden>
                GPL-2, see /usr/share/common-licenses/GPL-2 for full text
                Or Academic Free License 2.0:

GPL-2 cant be used because the whole thing is apache 2 (which is incompatible); so it must be Academic Free License 2.0 ... which looks copy-left. Question here is whether Academic License 2 has a similar requirement like GPL that requires all derived work to be distributed under Academic License 2. If there is no such requirement it should be ok, but IANAL.

Revision history for this message
Jonathan Riddell (jr) wrote :

I'm fine with keeping the XUL package in universe.

third_party/xdgmime is actually LGPL 2 or later, I've uploaded a new version with a corrected debian/copyright. LGPL should be able to link with an Apache licenced library and GPL 3 is compatible with Apache 2 licence.

Changed in google-gadgets:
status: Incomplete → In Progress
Revision history for this message
Alexander Sack (asac) wrote :

Thanks for fixing the licensing. LGPL 2 should be ok if xdgmime is not a consumer of apache licensed code, just not the other way around; also being a consumer would be possible with LGPL 3 or later ... so since its "or later" should be fine too.

@-xul binary in universe: Technically possible, I don't like the idea of having an unsupportable binary in universe built from a source in main; that should be really the exception; I would still prefer to see the -xul package being disabled for now or would that break rdepends in universe?

Changed in google-gadgets:
status: In Progress → Incomplete
Revision history for this message
Jonathan Riddell (jr) wrote :
Revision history for this message
Jonathan Riddell (jr) wrote :

Patch attached which would remove xul from it if that's what is needed.

Changed in google-gadgets:
status: Incomplete → New
Revision history for this message
Alexander Sack (asac) wrote :

rejecting google gadgets for the time being because mozjs doesnt have stable ABI/API policy - which should be easy to fix once they come up with a proper policy. Hopefully we can rely on mozjs in jaunty+1

Changed in google-gadgets:
status: New → Incomplete
Revision history for this message
James Su (james-su) wrote :

For now google-gadgets-xul is mandatory for google-gadgets-gtk. Removing it is not an option. However, I just noticed that xulrunner-1.9 (used by google-gadgets-xul) is actually in main rather than universe.
I'm wondering why it's not possible to put google-gadgets in main as well? I think the situation of google-gadgets should be similar than firefox-3.0, which is also in main and depends on xulrunner-1.9.

Revision history for this message
Alexander Sack (asac) wrote :

the problem is that it links against a lib that is shipped in pkglibdir ... (not libdir), which means that there are no official ABI/API promisses made on this.

Revision history for this message
James Su (james-su) wrote :

GGL doesn't have static binary linkage to libmozjs.so and libxul.so. Instead, it opens libmozjs.so dynamically (at runtime), just like what firefox and other similar applications do.
So I'm wondering why apps like firefox can be in main, while GGL can't.

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 314778] Re: Main inclusion for Google Gadgets

On Thu, Mar 05, 2009 at 03:18:39AM -0000, James Su wrote:
> GGL doesn't have static binary linkage to libmozjs.so and libxul.so. Instead, it opens libmozjs.so dynamically (at runtime), just like what firefox and other similar applications do.
> So I'm wondering why apps like firefox can be in main, while GGL can't.
>

ffox is maintained in sync with mozjs ... so its not independent and
abi breakage of mozjs will only happen together with the ffox
fix. However, thats special for firefox and other apps face the same
problem and are not in main. Only other apps that directly use mozjs
in main is probably epiphany ... which i know good enough to feel
comfortable to fix it when things really break.

 - Alexander

Revision history for this message
James Su (james-su) wrote :

A webkit backend has been implemented for GGL and will hopefully be released with the next version of GGL. Then the mandatory dependency between GGL and xulrunner can be removed. But unfortunately, webkit-1.0.1 is broken and will crash when running GGL. So it would be good if webkit in ubuntu can be upgraded to the latest version (1.1.x), then GGL can be built solely based on webkit instead of xulrunner.

Revision history for this message
Martin Pitt (pitti) wrote :

Jonathan, this MIR has become pretty stale. Is this still an issue?

Revision history for this message
Martin Pitt (pitti) wrote :

Timing out. Please reopen if it is still needed.

Changed in google-gadgets (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.