Bug#705565: Getting closure compiler back in testing?
gregor herrmann
gregoa at debian.org
Mon Dec 30 23:15:41 UTC 2013
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.
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
`- NP: Bob Dylan: Temporary like Achilles
-------------- 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/20131231/ccfc4fce/attachment.sig>
More information about the pkg-java-maintainers
mailing list