The ParaView 3.98.0 ebuild does not install the development headers/files. This means it is not possible to build ParaView plugins (which utilize these header files) against 3.98.0. Reproducible: Always Steps to Reproduce: Search for ParaViewConfig.cmake: $ find /usr -name "ParaViewConfig.cmake" $ find /usr -name "paraview-config.cmake" Actual Results: No files are found. Expected Results: The path to the relevant cmake files which are required for one to build ParaView plugins.
could you test if enabling "plugins" useflag solves this? I think it's PARAVIEW_INSTALL_DEVELOPMENT which is activated by "plugin" useflag. It should probably be enabled unconditionally then, but that needs some testing first.
With the plugins flag enabled the development headers still do not appear to be installed.
I think this is a typo in the ebuild PARAVIEW_INSTALL_DEVELOPMENT should be PARAVIEW_INSTALL_DEVELOPMENT_FILES afais...
yes, that works only question remains... should we keep this behind "plugins" useflag or do a seperate useflag for development files? opinion?
maybe even install them unconditionally
+*paraview-3.98.0-r1 (07 May 2013) + + 07 May 2013; Julian Ospald <hasufell@gentoo.org> +paraview-3.98.0-r1.ebuild, + metadata.xml: + fix install of headers and put it behind development useflag wrt #465258 ; + also fix compilation of plugins if all other useflags are disabled since nothing in the tree uses the headers, I think it's fine to put it behind a useflag for now, otherwise we will install them unconditionally
