As I haven't noticed an update to ming in the portage tree, I have decided to update the ming-0.3.0_beta2 ebuild to the 0.3.0 final version. This ebuild uses USE flags to denote which modules should be included with the package (this excludes the tcl module (which i cannot compile) and the ch module (the program for which is not in the portage tree). I added re2c to the build requirements for the php USE flag, as re2c is required for parsing, as the package states during configuration. Ming is a library to generate SWF files, with multiple modules, including php, python, java, and perl. In this ebuild, I have changed the way the php module is to be installed (if the user so chooses) by utilizing a different eclass. I have also cleaned up the ebuild a bit, with more references to ${PV} and such to allow for easier updating. I have been able to install each module included in the ebuild without trouble. But if the user wants the php module, they need either to disable the "ming" USE flag if they are installing php 5, or disable the "php" USE flag from this ebuild. The java-config patch is included to make sure the user's own javac will be used instead of the generic (and prob. incorrect) jdk specified in the java_ext Makefile. adam.
Created attachment 80953 [details] ming-0.3.0.ebuild
Created attachment 80954 [details, diff] java-compiler patch for correct javac
*** This bug has been marked as a duplicate of 121716 ***
