[Sugar-devel] [POLL] Non Sugar Platform activities in Activity Library
alsroot at member.fsf.org
Sat Feb 27 02:17:54 EST 2010
Before this moment some binary actitieis on ASLO bundle per architeture
blobs since binaries didn't weight much. But it doesn't play in case of
http://www.geogebra.org/ which is Java based application (bundling blobs
per architecture will mean 50M of dependencies and 5M of geogebra itself).
Since Sugar Platform can't grow endlessly, some dependencies can't be
included to SP(here Java). But bundling some of them will be pretty
overkill(Java, Qt etc). At the same time fetching dependencies on
demand(on first launch) could not fit to some deployment models.
So, the question is - how handle such non SP big dependencies in ASLO.
1) hmm.. what are you talking about, sugar is pure python environment
and blobs(not python) is evil, ASLO should handle only python
based activities(or activity should bundle all its dependencies)
2) activities that don't have bundled all dependencies should be
explicitly marked to not mess them w/ fully bundling ones
3) use complicated model when ASLO makes decision for every downloading,
should dependencies be included or not
Please suggest your variants and attach your +/-
More information about the Sugar-devel