Re: STOP INCLUDING EXTERNAL JARS IN YOUR JAVA PACKAGES!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Adam Heath <doogie@debian.org> writes:
> I have noticed that almost ALL packages include external .jars in their
> internal lib directories. This *MUST* stop. Yesterday. Last year.
Don't be so extreme... nothing is black and white.
This is a practice that is unfortunately common in the Java world.
To solve it...
Can I debian package require a specific version of another package?
Specifically if I have a package foo can it require *only* libbar-1.1.3.deb ???
Due to the WORA nature of Java applications, a lot of projects assume they are
the only package management system in existence. For example a lot of the
Jakarta projects ship with a whole bunch of .jars which are both incompatible
across projects and in their own ./lib.
> Lots of 'external' jars are not redistributable. You can't even have them in
> the source package.
This is a separate issue for debian-legal.
> I will be filing bugs on all java packages this weekend that do this. I will
> not exclude non-free packages either. This is something that must stop, and
> we must not allow upstreams to do so either.
I seriously hope that we don't have packages with non-free libs. If this
happens it would be a big issue :(
Kevin
- --
Kevin A. Burton ( burton@apache.org, burton@openprivacy.org, burtonator@acm.org )
Location - San Francisco, CA, Cell - 415.595.9965
Jabber - burtonator@jabber.org, Web - http://relativity.yi.org/
Copyright exists to improve science not to preserve the rights of the author.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt
iD8DBQE763fzAwM6xb2dfE0RApcYAKDSqd76gHoZLl6pQka40CUteFnOFACfX/fi
zzCwg6NDAFtMuOoQVflM6J8=
=RiND
-----END PGP SIGNATURE-----
Reply to: