Not yet. There might be a problem, still: the merging of .jar files.
You realise this kind of sounds like blackmailing, right? "I'll keep
blocking until I have been satisfied I have received enough answers" ;).
Personally I find this somewhat unpleasant ... but that might be just me.
Okay, let me explain myself:
A few days ago, I played with making an (for now: unofficial) package of
Jitsi 2.2 for Gentoo Linux, see .
From that, my impression was that Jitsi depends on a pile of
pre-compiled .jar files (which for 2.2 seems true). Many if not most of
the Java applications go that road, even smaller ones. I was assuming
that I would have to help cutting those out one by one myself if I
wanted to see Jitsi in Gentoo one day.
When the "Comment posted on jitsi" mail flew by, I was afraid that all
these pre-compiled .jars would end up in the final Debian package so I
contacted Kurt to make sure he was aware of the problem I assumed. I
didn't look close enough.
I didn't reply to his reply earlier because I was still searching for
answers in the build system. I am in no power to block anyone's actions
on the mentored Debian packaging process, if that wasn't clear.
Actually, I might be able to help you get Jitsi into Gentoo.
If my part here looked like that of an enemy to you until now, I hope
that we can start fresh.
Resolving (some) of the re-packing should fix
the problem. I am wondering: why are .jar files merged in the first
As explained, they are not merged. All these acrobatics happen because
we use OSGi and we need all jars that Jitsi uses directly to appear as
To best learn the differences from traditional .jars to OSGi bundles,
where would you send me? Anything to read that you can recommend in
On 29.06.2013 21:47, Emil Ivov wrote: