Bug#705565: Getting closure compiler back in testing?

[tony mancill]

On 12/30/2013 03:15 PM, gregor herrmann wrote:
> On Mon, 30 Dec 2013 12:03:13 -0800, tony mancill wrote:
> 
>>>>> The rename of the binary package from libclosure-compiler-java ->
>>>>> closure-compiler should probably be done now as well to get this out of
>>>>> the way well before the Jessie release.
> 
>> It means that the "closure-compiler" binary package is merely the
>> /usr/bin/ symlink and the dependency on jarwrapper.
> 
> Can't this be solved with a simple
>     Provides: closure-compiler
> in the libclosure-compiler-java package?
> (Or the other way round.)
> 
> Having a de facto empty package doesn't seem very appealing to me.

Hi gregor,

Yes, that will work, provided that no users of libclosure-compiler-java
have concerns with jarwrapper (and its depdendencies, thus
binfmt-support and fastjar) being pulled in when they only want the
library.  Given that all 3 packages are small, it's probably a non-issue.

Thanks for the suggestion!
tony

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 897 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20131230/1c0e23d3/attachment.sig>