[Sugar-devel] A Better ASLO
walter.bender at gmail.com
Sat Apr 26 11:03:23 EDT 2014
On Fri, Apr 25, 2014 at 11:52 PM, Jerry Vonau <me at jvonau.ca> wrote:
>> On April 25, 2014 at 8:54 PM Sam Parkinson <sam.parkinson3 at gmail.com>
>> On Apr 19, 2014 11:16 PM, "Tony Anderson" <tony at olenepal.org> wrote:
>> > Hi,
>> > Sorry I can't submit this to the lists - my internet provider doesn't
>> > sending to my email provider (sigh).
>> > There is an apparent policy to support the Sugar Activities distributed
>> > with builds 21 and 13 although not on ASLO. Walter has provided links
>> > to
>> > a version of TuxMath which works on the current builds, but this has
>> > not,
>> > far as I know been posted on ASLO.
>> OK, I might not be on the same page, but are you talking about activities
>> with different builds for different sugar versions?
> Think what Tony is referring to above are the versions of TuxMath &
> TuxPaint that are used in AU but require the underlying rpms to be present
> before the activity is usable. This would preclude the use in ASLO as all
> the dependencies may not be present in the OS and are not provided in the
> activity. To have these newer versions effective in ASLO sugar would need a
> way to install the needed underlying libraries(as rpms) but there is
> presently no way of doing this automatically right now and there looks to
> be no effort to add this support(1).
If someone is willing to work on this problem, I am confident it would
be accepted upstream.
>> > I would really like to see the limited available resources devoted to
>> > verifying which activities in ASLO work on build 21 (at least for XO-1)
>> > on build 13 (and on which XO (1.5, 1.75, and 4).
>> ASLO gets the compatibility for each bundle by reading through the code.
>> currently classify by:
>> * web activity
>> * gtk3
>> * new/old toolbars
>> [Suggestions welcome!]
>> > If necessary, ASLO should
>> > provide for multiple bundles where it takes a different bundle
>> > depending
>> > the build or XO model.
>> Providing a 'most recent version compatible with sugar XX' sounds like a
>> good idea.
> You have to take into account those activities which have libraries shipped
> with then, those tend to be architecture(x86_64,i386,ARM) specific. The
> activities mentioned above fall into that category, they used to ship with
> the libraries but in an effort to make the activity cross-arch compatible
> and reduce the size of the download those are not shipped with the
> libraries for all the supported arches, relying on the OS's packaging to
> supply those packages in advance at image creation time.
>> > While a fix was made for the incompatibility in activity.info, as far
>> > as I
>> > know it is not available for either build 21 or build 13 (i.e. to the
>> > base). It should be a simple matter to update the activity.info on the
>> bundles on ASLO to work with the distributed builds.
>> I lost you there.
>> BTW: what are these builds in sugar versions?
>> > Tony
> 1. http://bugs.sugarlabs.org/ticket/4623
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
More information about the Sugar-devel