Hi, I am attaching an enhanced ebuild for media-libs/qhull. This enhancement now creates and installs an additional .so shared library. For this reason, I have updated the version number on my submitted ebuild to qhull-3.1-r1.ebuild (from qhull-3.1.ebuild). I added this enhancement to the ebuild in anticipation of submitting an ebuild for the octave-forge package (octave.sourceforge.net) at a later date. The octave-forge package will automatically build with support for qhull - but only if a qhull shared library is found that has been created in the manner in which this enhanced ebuild creates it. Therefore, I modified the qhull ebuild to support future installs of octave-forge "out of the box", so to speak. The additions to the qhull ebuild that I am submitting were simply made based on instructions in the octave-forge package. It may be desirable to review how this ebuild creates the additional shared library, and improve/optimize the process at a later date. Unfortunately, I do not have enough knowledge about shared libraries or the octave-forge package to do this myself. Apart from creating the additional shared library, this enhanced ebuild does not change which version of qhull is installed, or anything else. I would be happy to answer questions pertaining to this ebuild. Brent Reproducible: Always Steps to Reproduce:
Created attachment 8130 [details] qhull-3.1-r3 (Update)
Sorry, description on ebuild attachment should read qhull-3.1-r1.ebuild (NOT qhull-3.1-r3.ebuild)
Can't get around to this anytime soon, sorry.
Hi Brent. Thank you for submission. I tested it and committed the chages. The ebuild is keymasked now, please test. George
Hi, Thanks for working on this. However, at this time, I'm stuck on a dial-up connection and probably won't be able to test this out in the near future. I'd love to help, but I'm kind of stuck, I'm afraid. Brent
In stable already
reclosing the bug
