[Sugar-devel] Why setup.py?

Aleksey Lim alsroot at member.fsf.org
Tue Apr 28 09:49:51 EDT 2009


On Tue, Apr 28, 2009 at 03:43:37PM +0200, Bert Freudenberg wrote:
> On 28.04.2009, at 15:33, SugarLabs Bugs wrote:
>
>> #795: Lack of setup.py in Etoys-101.tar.gz
>> Ticket URL: <http://dev.sugarlabs.org/ticket/795#comment:3>
>
>
> So the "fix" is to include this three-line script:
>
> #!/usr/bin/python
> from sugar.activity import bundlebuilder
> bundlebuilder.start()
>
> That does not make sense to me. Why should each and every activity  
> bundle include the same script?

In that case user(not only packager) has a standard way to bundle
installed activity(by command "./setup.py dist_xo") despite of the nature
of this activity.

Packager can have standard way to install it by command
"./setup.py install" as well

-- 
Aleksey


More information about the Sugar-devel mailing list