Bug#256283: [pylucene-dev] Re: PyLucence Debian Package

2006-02-07 Thread Andi Vajda
On Tue, 7 Feb 2006, Jeff Breidenbach wrote: Hi, I did a little digging. Package gcj-3.4 was removed from Debian Unstable on Aug 14, 2005 because it was Not Built by Source http://ftp-master.debian.org/removals.txt Since gcj is the critical path, this suggests to me that maybe gcj-4.x is

Bug#256283: [pylucene-dev] Re: PyLucence Debian Package

2006-02-05 Thread Andi Vajda
On Sun, 5 Feb 2006, Jeff Breidenbach wrote: Andi, how about distributing the binary package (.deb) from the PyLucene website while things are shaking out? Or perhaps Matthew can distribute from canonical.org, and have a link from the PyLucene homepage? This can be done immediately, allows

Bug#256283: [pylucene-dev] Re: PyLucence Debian Package

2006-02-05 Thread Andi Vajda
On Sun, 5 Feb 2006, Matthew O'Connor wrote: I compiled PyLucene 1.9rc1-7 for the i386, amd64, and powerpc Debian architectures. I created an APT repository because I figured it would be easier to manage. So if you add the follow instructions to your website they should make sense to any

Bug#256283: [pylucene-dev] Re: PyLucence Debian Package

2006-02-04 Thread Andi Vajda
On Sat, 4 Feb 2006, Jeff Breidenbach wrote: The gcj situation is more serious. No way in hell can we package the gcj runtime inside the PyLucene package. As far as I can tell this is a showstopper,although I'm curious what the gcj package maintainers have to say about the matter. Ah, if

Bug#256283: [pylucene-dev] Re: PyLucence Debian Package

2006-02-03 Thread Andi Vajda
On Fri, 3 Feb 2006, Jeff Breidenbach wrote: Another possibility - maybe - is to package an older version of PyLucene that depends on Java Lucene 1.4.3. However, I suspect there are likely to be similar issues and an upatched Java Lucene 1.4.3 will not be a viable build dependency either. The

Bug#256283: [pylucene-dev] Re: PyLucence Debian Package

2006-02-03 Thread Andi Vajda
On Fri, 3 Feb 2006, Matthew O'Connor wrote: Personally, I'm fine with it going into contrib. I'd like it to go into main but that's probably not feasible unless there's a DFSG-free JDK that could compile it. If Java Lucene exists as a Debian package already, then this problem must have

Bug#256283: [pylucene-dev] Re: PyLucence Debian Package

2006-02-03 Thread Andi Vajda
On Fri, 3 Feb 2006, Jeff Breidenbach wrote: Once there is a Debian Java Lucene 1.9 source package available, the PyLucene 1.9 package could be made to depend on it, unpack it, apply the patches, build it (and not install it) and then build itself. Seems pretty straightforward to me. Sorry,

Bug#256283: [pylucene-dev] Re: PyLucence Debian Package

2006-02-03 Thread Andi Vajda
On Fri, 3 Feb 2006, Matthew O'Connor wrote: I'll play around with trying to get this to work. Andi, when you normally compile the Lucene code which JDK do you use and on which platform (sorry if you answered this elsewhere)? Before I begin I want to verify I can at least reproduce what Andi

Bug#256283: [pylucene-dev] Re: PyLucence Debian Package

2006-02-03 Thread Andi Vajda
On Fri, 3 Feb 2006, Jeff Breidenbach wrote: I use Apple's JDK on Mac OS X, my main development platform. Oh yeah. There is one more technical factor to add into the mix, hopefully people's heads aren't ready to explode. Debian supports a lot of architecture, I think the current number is

Bug#256283: [pylucene-dev] Re: PyLucence Debian Package

2006-02-02 Thread Andi Vajda
On Thu, 2 Feb 2006, Jeff Breidenbach wrote: Hi Matthew, Good work on the package. However, I don't like that it starts with Java bytecode instead of canonical source code. Do you think it would be possible to have the PyLucene package use the Java Lucene package as a build dependency? With