[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

EpiGrass in Debian



Hi Flavio,

as you might probably know your EpiGrass program is integrated into
Debian GNU/Linux since some years.  It is currently maintained by the
Debian Med team[1] amongst other software which is useful in
epidemiology[2].  So at first, thanks for providing this interesting
piece of software which enriches the epedemiology part of Debian Med.

When packaging the recent version 2.0.1 I stumbled upon some things
which might need some polishing on your side which I would like to rise
here in this mail.

 1. Source of the documentation.
    This is a major issue because Debian ftpmaster does not accept
    "binary" files without source and proper license which is also
    the case for PDF files.  So we have to strip your documentation
    from the distributed source tarball which is a shame.  Is there
    any chance to include the LaTeX source inside the source tarball?
    This would be really helpful for our users.

 2. Remaining *.pyc and backup files
    Your tarball contains some *.pyc and backup files (*~) which is
    kind of boring when packaging because the clean target removes
    these files and you see several warnings by the packaging tools
    about differences in the original tarball and the unpackaged
    archive.  My guess these remainings are just an oversight on
    your side and I would recommend cleaning the tarball from these
    useless files.

 3. SQLAlchemy versus SQLObject
    I personally do not have any preference nor experience between
    these.  But when I realised that the SQLObject version in Debian
    is not really up to date and needs an upgrade for EpiGrass the
    Debian maintainer of SQLObject told me that he has dropped using
    it in favour of SQLAlchemy.  I just wanted to let you know that
    there are people out there who consider competing tools as better.
    I do not start any flamewar about this - just let you know.

 4. Minor patches
    I attached two patches which were created by the former maintainer
    of EpiGrass.  Apply them at your gusto to EpiGrass if you consider
    them useful.

Kind regards and thanks for providing EpiGrass

     Andreas.


[1] http://www.debian.org/devel/debian-med/
[2] http://debian-med.alioth.debian.org/tasks/epi

-- 
http://fam-tille.de
Author: V. Hiremath, C. Plessy.
Puropose: Make epigrass.desktop with FD.oâ??s Desktop Menu Specification.
 See http://standards.freedesktop.org/menu-spec/latest/index.html
Forwarded: https://sourceforge.net/tracker/?func=detail&aid=2785928&group_id=128000&atid=710326
License: same as Epigrass itself.
Index: epigrass-2.0b3/epigrass.desktop
===================================================================
--- epigrass-2.0b3.orig/epigrass.desktop
+++ epigrass-2.0b3/epigrass.desktop
@@ -1,5 +1,4 @@
 [Desktop Entry]
-Encoding=UTF-8
 Name=Epigrass
 Comment=Epidemics Simulator
 GenericName=Epidemics Simulator
@@ -8,4 +7,4 @@
 Type=Application
 StartupNotify=false
 Terminal=false
-Categories=Science
+Categories=MedicalSoftware;Science;Education;
Author: Author: V. Hiremath
Puropose: ?
Forwarded: no
License: same as Epigrass itself.
Index: epigrass-2.0b3/Epigrass/manager.py
===================================================================
--- epigrass-2.0b3.orig/Epigrass/manager.py
+++ epigrass-2.0b3/Epigrass/manager.py
@@ -22,7 +22,8 @@
 import encodings.utf_8
 import encodings.latin_1
 import dataObject as DO
-import sqlite3, MySQLdb
+import MySQLdb
+from pysqlite2 import dbapi2 as sqlite3
 #import pycallgraph
 
 # Import Psyco if available

Reply to: