Hi Peter, Thanks for prompt reply.
On 2022-03-24 17:16, Peter A wrote: > Instead of updating the "gradle" command could we just install a new > "gradle7" command that points to Gradle 7 instead? I don't think Gradle > is very backwards compatible so that might be the easiest solution. This would not help, I am afraid. Point with Gradle is that it needs itself to build newer versions of Gradle (circular dependency on itself), thus iteratively updating Gradle seems to be the only way to have newer Gradle in Debian. > For Jars that BoofCV downloads, It doesn't download anything outside of > Gradle. It uses a Gradle plugin i created called gversion to > automatically generate version info and a set of tools to do other auto > generation tasks: > > https://plugins.gradle.org/plugin/com.peterabeles.gversion > <https://plugins.gradle.org/plugin/com.peterabeles.gversion> Debian does not do out-of-git builds (.git directory is removed from sources prior to build), thus I guess this plugin would not be of much use (but I may be wrong). Nevertheless Debian precisely tracks source versions, thus version string could be injected via other means. > https://github.com/lessthanoptimal/Auto64Fto32F > <https://github.com/lessthanoptimal/Auto64Fto32F> This one I have already packaged for Debian, so the packaged JAR could be used. > Once the Gradle issue gets resolved we could then start adding these > dependencies. Sure. Best wishes, Andrius
