On 08/02/2016, Markus Koschany <a...@gambaru.de> wrote: > Am 07.02.2016 um 21:38 schrieb Emmanuel Bourg: >> Le 7/02/2016 17:21, Alex Vong a écrit : >> >>> You are right, it is more of a workaround than an actual fix, in case >>> we need to use gcj with clojure for some reason. By the way, may I ask >>> why all clojure version has +dfsg suffice? My guess is that because >>> the upstream tarball contains pre-built jar. Should we document it in >>> `README.source'? >> >> You're probably right about the removed jar files, but that's so common >> for the Java packages that we don't bother documenting it. > > Usually every package should provide either a get-orig-source target or > a README.source file if you repack the tarball. It is in general a good > idea to create a simple get-orig-source target in debian/rules like > > get-orig-source: > uscan --download-current-version --force-download > > If your debian/watch file is up-to-date and works it will download the > corresponding upstream sources. If you need to repack them, you could > also use the Files-Excluded field in debian/copyright, e.g. > > Files-Excluded: > *.jar > > and enhance the get-orig-source target like that: > > get-orig-source: > uscan --download-current-version --force-download --repack -compression > xz > > and all pre-built jar files will be removed while downloading the > original sources. > > This is usually an adequate documentation and a comfortable method to > quickly obtain the upstream sources. Since it is indeed rather common > for Java packages to include pre-built jar files, you can also omit the > +dfsg suffix. That's up to you. I > > Markus > >
Thanks you guys for the explanation. I don't know it is a common thing for java upstream tarball to include jar.
