Hi Kalle, Kalle Kivimaa schrieb:
You can either modify the .orig.tar.gz not to include the jars, or, IMO a better choice, modify the building process to use the Debian provided jars. I personally prefer keeping the orig.tar.gz as close to the original as possible (for JSPWiki all the Debian package does is repackage the zip as a tar.gz).
What do you mean by "modify the build process". Do you mean:1) Strip out all upstream binaries at the beginning of the build process and use references to Debian jars instead? 2) Leave upstream binaries and only manipulate classpath to "work around" upstream binaries?
If you use 1)- How do you get your deleted binaries back in during clean phase? AFAIK clean target has to reverse all changes the build process introduced.
If you use 2)- I find this procedure rather dangerous in practice as java build processes tend to involve complex classpath issues. It is probable that you cannot identify all the places where a jar file gets referenced during build. If you overlook anything you'd be in breach of Debian policy.
As long as the initial cleansing of the source tarball is automated, simple and reproducible I do not consider this a very far departure from the original source. IMO you don't modify the source at all you just strip binaries which are not part of the source anyway. (And you keep source package downloads considerable smaller for those who have a 250k-emerging-market-country internet access as I do ;-) ).
Regards, Florian