Scott, here are the notes I took while backporting interpid's current subversion-1.5.1dfsg1 pacakge:
debian/control: Change from default-jdk to java-gcj-compat-dev and default-jre to gij
debian/rules: Change from /usr/lib/jvm/default-jdk to /usr/lib/jvm/java-gcj
cp subversion-1.5.0dfsg1/debian/patches/java-build subversion-1.5.1dfsg1/debian/patches/java-build
debian/patches/series: uncomment java-build
All this hazzle is here, because in intrepid a new package 'default-jdk' has been introducded, which dispatches to the actually chosen JDK. In hardy, however, the build of the jni interfaces used gcj and need some extra patches.
For the control and rules file it simply boils down to use the files from intrepid's subversion-1.5.0dfsg1 package, which did not incorporates the switch to default-jdk.
And, yes, you might take my source packages from the clazzes.org repository, in case you don't want to reinvent the wheel ;-)
Scott, here are the notes I took while backporting interpid's current subversion- 1.5.1dfsg1 pacakge:
debian/control: Change from default-jdk to java-gcj-compat-dev and default-jre to gij jvm/default- jdk to /usr/lib/ jvm/java- gcj 1.5.0dfsg1/ debian/ patches/ java-build subversion- 1.5.1dfsg1/ debian/ patches/ java-build patches/ series: uncomment java-build
debian/rules: Change from /usr/lib/
cp subversion-
debian/
All this hazzle is here, because in intrepid a new package 'default-jdk' has been introducded, which dispatches to the actually chosen JDK. In hardy, however, the build of the jni interfaces used gcj and need some extra patches.
For the control and rules file it simply boils down to use the files from intrepid's subversion- 1.5.0dfsg1 package, which did not incorporates the switch to default-jdk.
And, yes, you might take my source packages from the clazzes.org repository, in case you don't want to reinvent the wheel ;-)
Best regards,
Wolfgang