[Sugar-devel] Activity packaging
pbrobinson at gmail.com
pbrobinson at gmail.com
Wed Aug 4 15:05:06 EDT 2010
On Tue, Jul 6, 2010 at 5:02 PM, Benjamin M. Schwartz
<bmschwar at fas.harvard.edu> wrote:
> 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.
PackageKit can already do that. There was a furore around 6 months ago
when someone enabled it by default for Fedora.
Peter
More information about the Sugar-devel
mailing list