Bug#733996: Generate a ‘closure-compiler’ binary package for the compiler program

[tony mancill]

On 01/04/2014 07:07 PM, Ben Finney wrote:

> The binary ‘closure-compiler’ package would install:
> 
> * the ‘/usr/bin/closure-compiler’ command (perhaps a symlink, as now)
> 
> * the manpage (not yet written?)
> 
> * the ‘README’ file (or some subset the describes running the compiler from
>   the command line)
> 
> * maybe others
> 
> My main point in responding to your message is: the binary
> ‘closure-compiler’ package will not be empty. It will need to install files
> distinct from the ‘libclosure-compiler-java’ package.

Hi Ben,

There isn't currently a manpage - the documentation I've seen regarding
using it refers to invoking it as a jar file (see [0], and more
generally [1]).  Given that all of the upstream documentation is focused
on invoking it as a jar file, I think we're on our here, at least at the
start.

I agree that the package should have a manpage if we're going to
continue to provide the /usr/bin/ symlink.  Daniel added this in the -3
upload.  If you or Daniel can contribute a manpage, that would be great.

Currently, that manpage would be the only file in the binary package, as
/usr/bin/closure-compiler will remain a symlink to the executable jar,
so it's still going to be a very small package.

Cheers,
tony

[0] https://developers.google.com/closure/compiler/docs/gettingstarted_app
[1] https://developers.google.com/closure/compiler/



-------------- 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/20140104/a4f4058e/attachment.sig>