(OLD) (ARCHIVED) Puppy Linux Discussion Forum

[ljfr]

Hi sidders,

this PM was related to gcompris version 8.4.12, which still needed gstreamer but I had excluded some plugins and extras dependencies.

For version 8.4.13, there is no need for gstreamer at all, the sound is handled by SDL, I posted here the list of required dependencies/packages:
http://www.murga-linux.com/puppy/viewtopic.php?t=40490&start=90

note for the last tuxpaint, I have not compiled the configuration module yet...

regards,

[technosaurus]

Note for developers: I will post this here first since a lot of python is used in HSB. When you package a python program for use in a read only SFS or installation as a pet (possibly a RAM drive).... the first time the <whatever>.py is run, it will create .pyc and/or .pyo files (which are compiled bytecode and optimized bytecode respectively) This leads to filling up the RAM drive pretty quickly.

Fortunately you can package the python programs with only the .pyo or .pyc instead of the .py files - Python will find and use them. The only nuance is that you will have to change the startup script to point to the .pyc or .pyo or just leave that one .py (to comply with gpl you should also make the sources "available")

Oh yeah ... and it will start faster too.

[ljfr]

Hi, technosaurus, you're right, I should package with pyc and pyo files,
I uploaded amended packages at:
http://ljfr2.perso.neuf.fr/pet_packages-4/general/

for those who installed some Pets I packaged, here is a small script that scan your puppy and if any of this pet:
Python-2.5.4-i486, pysqlite-2.5.5-i486, pygtk-2.12.0-i486, pygobject-2.20.0-i486, pygame-1.8.1-i486, pycairo-1.6.4-i486, numpy-1.3.0-i486, SQLAlchemy-0.5.6-i486, gcompris-8.4.13-i486, pysycache-3.1.0-i486, childsplay-1.4.0-i486
is installed and will compiled pyc, pyo and update the /root/.packages/file for a clean uninstall.

NB:by the way it seems that uninstalling a pets doesn't erase some empty folders.

regards,

[technosaurus]

@ljfr - You really only need one or the other of pyc or pyo (and then you can remove the corresponding .py) - typically .pyo are a bit smaller because they are basically the .pyc with some debugging features removed (not usually that much of a difference at the moment) For pets while using a pupsave file its not too big of a deal, but when remastering a puplet you should notice a significant speed boost especially if you want to keep the kids from messing things up by booting with pfix=ram

[ljfr]

@technosaurus, I agree, if it was just for me I would just use pyc files unless I want to change few things in the code, then would get py files.

For packaging, looking around:
http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html
http://en.opensuse.org/Packaging/Python
they go for .py + .pyc + .pyo (in the package directly or with a post install script).

I still want to keep py files for transparency, If size really matters, you can easily tweak the previous script to erase py or pyo or pyc, and modify the /root/.packages/files accordingly...or repackage the pet without them before installing. Your call.

NB: On the Python-2.5.4 packages the difference between py files only and (py + pyc + pyo) files is 6M compressed, 25M uncompressed.
[numpy and SQLAlchemy ~ 1M compressed, for other packages, differences are really small].

[sidders]

Could i ask if the 'test' folder in Python is important?. I removed it (when looking to trim some fat) and all seems to be well with gcompris etc.
Or was that a really stupid idea

I ran the script with a new save file. Could i manually remove the py files from the origonal sfs and copy the new pyc and py files from the save file and recreate the sfs. Basically remastering manually.

[technosaurus]

Yep, That is basically what I did with the last kiosk version that I respun.

[sidders]

Started a new thread with a pre-release
http://www.murga-linux.com/puppy/viewtopic.php?t=49124