Hi Thomas,

Le 29/01/2016 13:08, Thomas Goirand a écrit :

> The problem doing this, is that if antlr3 evolves and the Python module
> has some kind of adaptation, then we need to release them in sync.

You are right and this has already happened. For example antlr 3.5.2 is
incompatible with antlr 3.2, and we worked around this issue by
introducing an antlr3.2 package.

The good news is that antlr 3.x is not going to evolve anymore, upstream
is now working on antlr 4.x.


> Also, there's no separate tarball for the antlr3 Python package, it's
> all-in-one.

Well, couldn't the tarball of the python-antlr3 package simply consist
in the content of the runtime/Python3 directory? Repacking the tarball
isn't difficult. That's how the C runtime was packaged I believe
(libantlr3c).

Emmanuel Bourg

__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to