Hi Rich.
On 9 June 2016 at 12:59, Richard W.M. Jones <rjones@xxxxxxxxxx> wrote:
>
> I maintain a package which comes with some benchmarking tools. I
> would like to package these, but they have very generic names like
> "boot-benchmark", "analysis". Also the tools are very specialized --
> you would only want them if you already know you need them.
>
> I wonder if people have opinions on the best way to package these. It
> seems to me the options are:
javapackages-tools and javapackages-local have many small programs in
/usr/share/java-utils.
Most of the programs are called from rpm-macros:
$ rpm --eval '%{mvn_build}'
/usr/bin/python3 /usr/share/java-utils/mvn_build.py
But they can be called directly and makes them good for debugging and
testing, many of the programs also have man pages:
$ whereis mvn_build
mvn_build: /usr/share/man/man7/mvn_build.7.gz
Jonny
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
