Last version in my portage tree seems to be quantlib-0.3.0 (last emerge sync on 2005-01-02, 12:38 GMT). This version is over two and a half years old. Last bugzilla entry for version bump to 0.3.5 I found is here: http://bugs.gentoo.org/show_bug.cgi?id=46889 Version 0.3.8 is out. As noted before, the file name has slightly changed (no longer QuantLib-X.X.X-src.tar.gz but QuantLib-X.X.X.tar.gz), also to me it looks as if it now depends on dev-libs/boost. An ebuild with these very small changes is attached. There is also a lot of documentation that could be built with doxygen. I played around with getting that into the ebuild via the "doc" use flag, but in the end had problems with dohtml etc because there were too many files to copy ("too many args"), and I didn't have time to get it to work. I also attach an ebuild for QuantLib-Python - the Python bindings for QuantLib.
Created attachment 47366 [details] proposed ebuild quantlib-0.3.8
Created attachment 47367 [details] proposed ebuild quantlib-python-0.3.8
This bug represents a good reason to search the database before reporting. :) I too, noticed the ancient version in portage, and came to bugzilla to file a request for an ebuild of the current release, and much to my surprise, I found someone else had beaten me to it by just a few days. Please count this as another vote for a quantlib 0.3.8 ebuild.
Hello, I submitted this bug quite a while ago and after syncing today, it looks to me like this still hasn't been updated. The version in portage is now 3 years old. Honestly, the changes in the ebuild are very small, but it needs to be updated. Don't you want to put this in the portage tree?
Quantlib 0.3.9 has been released. The ebuilds attached above can simply be renamed: quantlib-0.3.8.ebuild -> quantlib-0.3.9.ebuild quantlib-python-0.3.8.ebuild -> quantlib-python-0.3.9.ebuild Both seem to download everything properly and build fine with this small change. Max
Since this package has no current maintainer in metadata.xml, I am taking it.
*** Bug 46889 has been marked as a duplicate of this bug. ***
Alright, got 0.3.9 to compile with gcc-4. Ran quantlib-test-suite and got no errors. I dropped alpha, mips and hppa from keywords because of dev-libs/boost dep. I'll look into it to see if boost can be keyworded to support those architectures. Bumping in cvs. I see there are bindings for all types of things: ruby, python, .NET. Do you think that a) they are necessary b) they should be in one big bindings package?
*** Bug 45962 has been marked as a duplicate of this bug. ***
Keyword request for dev-libs/boost in bug 91936.
hppa, mips, would you mind keywording quantlib-0.3.11? It seems boost has the necessary keywords by now.
Removing ~mips keyword from 0.3.0 as we have no way of testing and package appears to have no use or deps for mips atm. Drop us a note/bug if this ever changes.
(In reply to comment #12) > Removing ~mips keyword from 0.3.0 as we have no way of testing and package > appears to have no use or deps for mips atm. Drop us a note/bug if this ever > changes. Seems the same is true for hppa[1]. [1] http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-libs/quantlib/quantlib-0.3.0.ebuild?r1=1.4&r2=1.5
