Hi Radu, On 30 Oct 2012, at 09:10, Radu Gheorghe <radu0gheor...@gmail.com> wrote:
Yeah, that's a problem indeed. I saw it after opening this bug. I've had a look into it a bit deeper. There are a few problems with packaging based on the upstream tarball as it stands. The biggest seems to be that it ships pre-compiled libsigar. There isn't a pre-existing package for this. I have yet to take a detailed look at it but at first glance it seemed like it would be a reasonably simple exercise to create. I have yet to check for packages for all of its Java dependencies. Yes, I'm actually more involved with ES now than I was a while ago. I almost forgot about it because I didn't see any reaction to this bug. Until now :) Excellent. Having someone involved upstream will certainly smooth the process :) That sounds really nice, thank you. Maybe we can come up with a plan on how to go further. Perhaps you would be able to take a look through http://wiki.debian.org/UpstreamGuide ? Of particular interest is the section on Java. I will have a quick stab at a very basic package and identify any obvious blockers for us. If it looks doable I suggest we convert this to an ITP. Regards, Nick
