[Debian-med-packaging] Comments regarding openmrs_1.6.1-1_amd64.changes

[Mike O'Connor]

On Tue, 9 Nov 2010 17:01:01 -0600, Misha Koshelev <misha680 at gmail.com> wrote:
> Dear Luca et al,
> 
> Thank you very much for your well thought out comment regarding the
> JAR files. You are correct, the JAR files do indeed include .class
> files, which are indeed binary artifacts.
> 
  [ .. snip .. ]

> 
> You will also note that existing Debian Java packages actually seem to
> include such "binary" components in their source packages as well.
> 
> One example, referenced by the Java Packaging team as a "good example
> of up to date projects" is:
> http://packages.debian.org/testing/misc/weirdx
> (see http://wiki.debian.org/Java/ExamplePackages for reference)
> 
> You will note that, if you browse the "source tarball":
> http://ftp.de.debian.org/debian/pool/main/w/weirdx/weirdx_1.0.32.orig.tar.gz
> there is a jar file with similar binary artifacts (misc/weirdx.jar).

Perhaps you are misunderstanding the crux of the issue.  A source
package including binaries is ok if it also includes the source for
those binaries.  A binary package including binaries is ok if those
binaries are build from source during the package build.

I think the initial concern was that your upstream source contained
.class files for which there might not be source files (.java files).
If that is the case, the upstream source will need to be modified
(either to omit the binaries for which source isn't included, or to
include the source).

I looked at the source package you pointed at, and at a quick glance I
only see the one jar (misc/weirdx.jar), and it looked like the .java
files also existed in the source package for the class files contained
in the jar.

stew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20101109/5a3ca42f/attachment.pgp>