Hi Aaron! I've done preliminary packaging of PyEPL. Debian package is available from http://itanix.rutgers.edu/rumba/dists/unstable/perspect/binary-i386/science/python-pyepl_1.0.9-0.1_i386.deb and the changes I had to do to make it build into the package (including debian/ packaging directory) are available from http://itanix.rutgers.edu/rumba/dists/unstable/perspect/source/science/pyepl_1.0.9-0.1.diff.gz
Please revise the changes I had to make (omitting debian/ directory): the main problem was absent "cleaning" procedure. Changes I made are quite cruel and are far from being an ideal solution. In general, if someone want to track the package by installing it via standard debian means (before it enters official Debian) needs to add deb http://itanix.rutgers.edu/rumba/ unstable perspect deb-src http://itanix.rutgers.edu/rumba/ unstable perspect to their apt/sources.list There are quite a few points I need to discuss and have resolved before the package becomes appropriate for inclusion in Debian. Most of them are in debian/TODO file within the source (after applying my diff) Here they are and I would really appreciate your help on resolving them: * Clarify the destiny of pyODE-0.35cvs-2.tar.gz if it is possible to migrate to the fresh version (projects merged) http://pyode.sourceforge.net/ for which RFP wnpp bug was filed long ago http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=329013 Why is the full source (.tgz) is carried with pyepl anyways if there is alrady ode.pyx within the pyepl tarball? If updated pyODE is not suitable to be used with pyepl, could upstream at least get rid of .tgz and just keep original ode.pyx (it includes license warning, and can be accompanied with license file: I would just refer to the LGPL file provided with Debian) * Clarify the situation with shipped non-free font: code/resources/font.ttf * To don't byte-compile: dh_python will do that... but I am not sure on how to turn that off in setup.py...? * Proper split out of shared libaries (.so) + (.h) files I believe that at the end I will have to do such split into libepl, libpyepl-dev and then making python-pyepl depend on libpyepl. Might need to clarify at [EMAIL PROTECTED] * Proper "clean"-up procedure Well... though it is not required (or in other words "could be avoided") -- it is good to have proper clean-up procedure and original Makefiles were missing clean target. Besides that setup.py is not tailored to provide proper cleaning. Temporary fix was applied but proper solution would be better * Compile and package manual into -doc Compilation failed on first attempt: more investigation is necessary > make jade -t sgml -d /usr/share/sgml/docbook/stylesheet/dsssl/modular/html/docbook.dsl pyepldoc.sgml jade:pyepldoc.sgml:10:0:E: character "<" not allowed in declaration subset jade:pyepldoc.sgml:31:2:E: character "<" not allowed in declaration subset jade:pyepldoc.sgml:40:8:E: end of document in DTD subset make: *** [pyepldoc.html] Error 1 Installed: ii docbook-dsssl 1.79-3 modular DocBook DSSSL stylesheets, for print ii jade 1.2.1-47 James Clark's DSSSL Engine Besides that, I have tried to run example scripts using PyEPL installed from my Debian package and bugs.py works properly but hw.py example shipped with source tarball fails... and the reason why is that the examples shipped within source tarball are different from the ones within pyepl_sample_code-1.0.9 > diff pyepl-1.0.9.origg/code/documentation/source/examples/hw.py pyepl_sample_c ode-1.0.9/hw.py 8a9 > exp = Experiment() could we unify those? :-) On Tue, 14 Mar 2006, Aaron Geller wrote: > Hi Yaroslav. > You can run PyEPL experiments in either of 2 modes: with or without > synchronizing to the monitor refresh. If you run > with synchronizing enabled, the function actually blocks until the screen > update has occured; there is no need to guess > as to how long the delay due to the refresh is. We know based on when the > function returns. > Syncing to the screen refresh is important for psychophysics experiments, but > if you want to minimize delays due to > screen updates, you can turn this functionality off with the --no-screen-sync > flag at the command line. > With respect to debian package, nobody has yet packaged pyepl in a .dpkg. We > would love to have skilled debian users > help us with linux deployment. We will be in touch! > Thanks for your interest, > Aaron Geller > PyEPL Project Maintainer -- .-. =------------------------------ /v\ ----------------------------= Keep in touch // \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User ^^-^^ [175555]
