Bug#705565: Getting closure compiler back in testing?

[tony mancill]

On 12/30/2013 11:35 AM, Thomas Koch wrote:
> On Monday, December 30, 2013 10:19:53 AM Daniel Pocock wrote:
>> Tony made some commits in Git and it appears he is working to resolve this
>>
>> 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.
>>
>> I've made the changes for a rename on a branch called "pkgrename" and
>> pushed that into Git
>>
>> Tony, are you making another upload shortly, would you like to merge
>> pkgrename perhaps?
> 
> closure compiler is also a library dependency, e.g. of gwt. It might be a good 
> idea to provide two binary packages, one for the library jar and another one 
> for the manpage + executable.
> 
> Regards, Thomas Koch

Hi Thomas, Daniel,

I agree with Thomas' suggestion.  I'm not sure what the FTP team will
think of the very small binary package (the next upload will go through
NEW), but adding a binary package with just the manpage + JRE and
jarwrapper dependency feels like the right thing to do.

Any thoughts about whether it's better to update to a newer upstream and
then rename, or rename first?

Cheers,
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/b6758ae6/attachment.sig>