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

[Ben Finney]

On 04-Jan-2014, tony mancill wrote:
> On 01/04/2014 07:07 PM, Ben Finney wrote:
> > […] the binary ‘closure-compiler’ package will not be empty. It will
> > need to install files distinct from the ‘libclosure-compiler-java’
> > package.
> 
> 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.

A small package shouldn't be a problem, if the package serves a purpose
distinct from any other package.

Since the binary ‘closure-compiler’ package will have distinct dependencies
from the dependencies of the other binary packages, be in a separate
section of the archive, etc. the small size shouldn't disqualify it from
entry into the archive.

-- 
 \          “A thing moderately good is not so good as it ought to be. |
  `\        Moderation in temper is always a virtue; but moderation in |
_o__)                       principle is always a vice.” —Thomas Paine |
Ben Finney <ben at benfinney.id.au>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20140105/489a7e6b/attachment.sig>