Earl, sorry for the delay responding. No, there's no need to build a
new .deb package with each commit. You build new packages whenever
you feel like it. I am using a snapshot of the trunk from a few
months ago (svn rev 219230) myself.
Re: the JDK, I'm still talking about using Sun's JDK, not kaffe or
any of those other versions. It's just much easier to deploy on
Debian/Ubuntu/etc if it's in .deb form. The "java-package" package
builder does exactly that. Feed it a binary build of JDK 1.5 from
sun.com, and the result is sun-j2sdk1.5.deb, which you can install on
your own private package server (easy to set up).
But this is getting off-topic for nutch-dev, I think. Let's follow up
privately or on nutch-users (which I need to subscribe to... :).
--Matt
On Sep 13, 2005, at 2:42 AM, Earl Cahill wrote:
Earl, I've been building binary .deb packages from
Nutch 0.7 trunk
straight from ant for a few months now. It makes
deployments to
Ubuntu much smoother.
Sorry to be dumb, but that seems to mean you would
need to make new packages for pretty well each commit?
I can see that more as the project gets perhaps a bit
more stable.
Combine that with the
"java-package" utils for
deb-ifying the JDK, and your rollouts will be
greatly simplified.
Maybe it was just my athlon being weird, or could
definitely be my lack of java experience, but I tried
kaffe, java-common, j2re and free-java-sdk to no
avail.
Needless to say, I would be more than happy to strip
the sun java stuff out of my tutorial and just getting
a few more packages from apt-get. It is sounding like
you have some pure apt-get method. Guessing you use
universe, but what packages suffice for you? I will
gladly give them a shot.
Thanks,
Earl
--
Matt Kangas / [EMAIL PROTECTED]
