The version now present on the tree (2.0.23) will not compile with the newest version of CMake, so when CMake is updated, something needs to be done about jasper: or we remove it from the tree or we update it, otherwise it will break the build of something else when it's pulled in as a dependency.

I found out about this package because it is pulled in by the CMake ebuild itself when the USE flags emacs or qt5 are enabled.

Reasons to remove it:

• media-libs/jasper is a library, including a command line utility, to convert images to and from the format JPEG2000.
• media-gfx/imagemagick[jpeg2k] also provides a library and a command line utility that will convert to and from JPEG2000.
• Gentoo has already removed it from their tree.
• Who ever really uses JPEG2000 for anything?

Reasons to keep it, up to date:

• It is in right now in active development, but without any major changes. It's mostly bug fixing.
• I literally just did this:

  cp jasper-2.0.23.ebuild jasper-3.0.6.ebuild

  which is a jump of 13 releases, and still, it compiled cleanly without warnings. This means that if it is autogenned, it will probably be a very low maintenance package.

• The autogen itself would be really easy to write: it's a CMake based package from a GitHub repository with well behaved tags names, release names and assets names.
• The following packages currently have it as an optional dependency, associated with the jpeg2k use flag:

• dev-games/openscenegraph
• x11-libs/gdk-pixbuf
• media-libs/devil
• media-libs/libraw
• media-libs/netpbm
• net-proxy/ziproxy
• sci-libs/grib_api
  The following one has jasper as a hard dependency:
• sci-electronics/eagle

...therefore, it might be easier to autogen it than to remove the dependency from these packages, even considering the fact that most of them are candidates for beard-trimming themselves.