[Sugar-devel] Help Needed adding a module to my Activity
tony_anderson at usa.net
Mon Aug 8 10:09:34 EDT 2016
Sugar activities are written in Python. Python modules are installed by
setup.py. The cases you are describing are special exceptions where an
activity includes a binary module (e.g. box2d or java runtime).
ASLO could provide alternate bundles for XO-1 and XO-1.5 and for XO-1.75
and XO-4. This requires someone to update the interface to provide this
information. It would also be nice if the ASLO interface showed the
supported versions of Sugar (something which is now impossible).
ASLO has been serving Sugar users well for nearly a decade.
On 08/08/2016 03:42 PM, Sebastian Silva wrote:
> El 08/08/16 a las 01:30, Sam Parkinson escribió:
>> Side note: It would be so much better if Sugar activities could just
>> declare dependencies. Just say something like "bindeps=fontmake". If
>> we just made them all into RPMs/DEBs and had a AppStream based store
>> interface ... that would be nice. ASLOv2v2 is just something
>> automatically building rpms and debs?
> The practice of embedding dependencies within bundles is really bad, it
> implies duplication where two activities share a dependency, or, in the
> case of multiple architectures, bloat. Finally it makes it nearly
> imposisble to account for bugs and vulnerabilities.
> Once upon a time Aleksey Lim proposed the "recipe" specification to
> overcome activity.info deficiencies. I wonder if it would be possible to
> reuse some of his work:
> I saw it working in alpha verision. Currently Hexoquinasa OS image
> package list is built in part from dependencies declared in recipe files.
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
More information about the Sugar-devel