[Sugar-devel] [ASLO] Release Oopsy-1

James Cameron quozl at laptop.org
Mon Jan 21 21:23:18 EST 2013

On Tue, Jan 22, 2013 at 12:30:02PM +1100, forster at ozonline.com.au wrote:
> A developer makes a version of gcc that can run from
> ~/Activities/oopsy.activity , this is included in oopsy.xo
> bundle(maybe 2 versions x86 and ARM), at install time (optionally
> oopsy checks for the presence of gcc and if not present then) oopsy
> installs gcc at ~/Activities/oopsy.activity .
> There is a 30MB bloat of oopsy.xo bundle and a possible 30MB bloat
> of the installed Activity.
> Right?

I have not measured gcc, but 30 MB seems excessive for a C compiler.
Perhaps there are some files that are not required by the activity,
such as some libraries, that need not be packaged.

There are other C compilers too.  Without knowing the C standard that
Oopsy encourages, or the APIs that are used, I can't comment on which
are appropriate.

Full functionality costs space.  Installing gcc is going to cost
anyway, no matter which way you do it, yum or not.

A 30 MB loss isn't much with the current systems being produced.

James Cameron

More information about the Sugar-devel mailing list