Ainsi parlait Oti :
> [ Guillaume Rousse ]
> > I'm the jpython package maintainer for jpackage project (see
> > http://www.jpackage.net). The current jpython release format (gui installer)
> > is a
> > pain to deal with, and i'd strongly advocate to also provide standard
> > source
> > and binaries tarball alongside.
> Oops, I truly believed I am the only one still using JPython <wink> -
> not for long any more, by the way.
Oops, sorry, my fault, i once again confused jpython and jython. I meant
jython (the current one).
> > I've already asked for this before, response was "too many work for
> > us,
> > you're the only one interested". If i provided an ant target
> > automating this
> > task, would this request be reconsidered ?
> > Also, you're duplicating oro classes in jpython.jar. I understand
> > that is
> > practical, but it is really not a proper system administration
> > practice.
> > Could you please remove those classes, and just explain you need oro
> > classes
> > in your classpath ?
> jpython.jar used com.oroinc.* classes, jython.jar uses org.apache.oro.*
> classes. It is really handy to have the right version included, IMHO.
My point was to *not* include them, to avoid endless code duplication. Think
as static linking vs dynamic linking, if you prefer.
> I think there is no need to use the gui installer (beside the fact that
> there is also a command line version): Just rename jython-21.class to
> jython-21.jar and extract/remove whatever you like.
Once again: i'm not asking how to deal with the class file, as i know how to
do it, but this is painful, and i have no real knowledge of what is jython
and what is packaging artifact. I'm asking to have standard source and
binaries tarball for future jython releases. And i'm even volonteering myself
to provide relevant ant target to make maintainer's life easier if they agree
to use them.
Guillaume Rousse <rousse@...>
GPG key http://lis.snv.jussieu.fr/~rousse/gpgkey.html