Activity packaging

[Benjamin M. Schwartz]

On 07/06/2010 11:51 AM, Bernie Innocenti wrote:
> Ok, I think the requirements for activity bundles could be:
> 
> 1) Support multiple CPU architectures
> 
> 2) Support multiple distros (and different versions of same distro)
> 
> 3) Centralized build cluster (submit one source package, get multiple
>    binary packages)
> 
> 4) Support inter-bundle dependencies
>    (e.g.: GCompris + voices, OOo4Kids + dictionaries)
> 
> 5) Support activity <-> OS dependencies (e.g.: espeak for Speak,
>    squeak for etoys...)
> 
> 6) Work with any programming language (setup.py is python-centric)
> 
> 7) Easy to learn for activity writers without too much distro-hacking
> experience
> 
> 
> These requirements would fit well both rpm and deb, with OpenSUSE Build
> Service or their native build clusters.

I think you are missing an important requirement: installation without
elevated permissions.

--Ben

P.S. This cross-posting is getting ridiculous.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.laptop.org/pipermail/devel/attachments/20100706/892a9ae6/attachment.sig>