Bug#256283: [pylucene-dev] Re: PyLucence Debian Package
Jeff Breidenbach [breidenbach@gmail.com] said:
> Andi, Debian's infrastructure is designed such that a source package is not
> allowed to be a build dependency. Matthew, please file a wishlist bug against
> swig, requesting a version update.
I think I confused the issue. Unstable has SWIG 1.3.27.
PyLucene requires version 1.3.24, which is older. So I
don't think a wishlist bug is appropriate here.
Also, PyLucene requires GCJ 3.4.x, x >= 3. However,
unstable has 4.0.2. This is an even more egregious issue
because even providing a .jar in the source package would
not be enough since that version of gcj would produce bad
results (everything compiles, nothing works).
I don't think a build on unstable is currently possible.
PyLucene requires versions of GCJ and SWIG which are too old
to be in Debian unstable.
So, I see the open issues as follows:
1. PyLucene and/or SWIG needs to change so that the
version of SWIG in Debian Unstable can be used.
2. PyLucene and/or GCJ 4.0 needs to change so that
the version of GCJ in Debian Unstable can be used.
3. PyLucene may or may not compile from source with a
free software JDK (e.g. free-java-sdk package).
Of course, as time passes, the particular version of GCJ and
SWIG in Unstable will change.
Unless I'm missing something, I don't think making a package
for Debian Unstable is possible right now unless everything
PyLucene needs is statically linked into its .so. The way
Andi currently distributes binary packages won't fly in
Debian; at least I can't imagine having the pylucene package
provide /usr/lib/libstdc++.so.5 would be okay with folks.
FWIW, it is possible to build a package for Debian Stable
(Sarge), but that's just b/c Sarge includes all the old
stuff PyLucene needs.
So I'm at a loss as to what to do, other than wait. Anyone
else?
-matthew
Reply to: