Opened 15 years ago

Closed 15 years ago

Last modified 11 years ago

#795 closed defect (fixed)

Lack of setup.py in Etoys-101.tar.gz

Reported by: alsroot Owned by: bert
Priority: Low Milestone:
Component: Etoys Version: 0.84.x
Severity: Minor Keywords:
Cc: Distribution/OS: Unspecified
Bug Status: Needinfo

Description

its not a huge problem but jhcovnert uses unified method to package all activities and so needs setup.py

Attachments (1)

sugar-795.patch (209 bytes) - added by alsroot 15 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 Changed 15 years ago by alsroot

  • Version changed from Unspecified to 0.84.x

comment:2 follow-up: Changed 15 years ago by bert

  • Bug Status changed from Unconfirmed to Needinfo

What does setup.py do? The only thing you need to do to install the Etoys activity is unpack the bundle in the right place.

I searched the Sugarlabs wiki but it only mentioned that setup.py is used for some tasks in Python activities. You should probably fix jhconvert to not rely on setup.py. If that's too hard, point me to a spec (preferably on a semi-official Sugarlabs site) and I'll see what I can do.

comment:3 in reply to: ↑ 2 Changed 15 years ago by alsroot

Replying to bert:

What does setup.py do? The only thing you need to do to install the Etoys activity is unpack the bundle in the right place.

I searched the Sugarlabs wiki but it only mentioned that setup.py is used for some tasks in Python activities.

btw, thats a standard way to bundle activity(if activity has already installed) and install it(in distro meaning) :)

You should probably fix jhconvert to not rely on setup.py.

it should complicate process a bit - the only one activity that doesn't have setup.py is sugar-etoys

If that's too hard, point me to a spec (preferably on a semi-official Sugarlabs site) and I'll see what I can do.

well, its not distro specific stuff but sugar itself
see simple patch which I use

Changed 15 years ago by alsroot

comment:4 Changed 15 years ago by alsroot

and.. I meant sugar-etoys not etoys intself

comment:5 follow-up: Changed 15 years ago by bert

  • Status changed from new to accepted

Still no word on what setup.py actually does. How it is called, which options it supports etc. See
http://lists.sugarlabs.org/archive/sugar-devel/2009-April/014096.html

comment:6 in reply to: ↑ 5 Changed 15 years ago by alsroot

Replying to bert:

Still no word on what setup.py actually does. How it is called, which options it supports etc. See
http://lists.sugarlabs.org/archive/sugar-devel/2009-April/014096.html

just type:

$ ./setup.py
 
Available commands:

build                Build generated files
dev                  Setup for development
dist_xo              Create a xo bundle package
dist_source          Create a tar source package
fix_manifest         Add missing files to the manifest
genpot               Generate the gettext pot file
install              Install the activity in the system

(Type "./setup.py <command> --help" for help about a particular command's options.

comment:7 Changed 15 years ago by alsroot

That would make sense. In fact, I previously made a mkDist.py script
(in the etoys repo) that would call the bundle builder to create an xo
bundle. It sets the dist_dir variable in the Config object. How would

I set the dist_dir when using setup.py?

dunno, I build .xo only for uploading it to ASLO, so I call "./setup.py dist_xo" by hands

comment:8 Changed 15 years ago by tomeu

  • Milestone changed from Unspecified by Release Team to 0.86
  • Priority changed from Unspecified by Maintainer to Low
  • Severity changed from Unspecified to Minor

comment:9 Changed 15 years ago by alsroot

  • Resolution set to fixed
  • Status changed from accepted to closed

Etoys-105 has setup.py

comment:10 Changed 11 years ago by dnarvaez

  • Milestone 0.86 deleted

Milestone 0.86 deleted

Note: See TracTickets for help on using tickets.