On Apr 7 2011 wt-3.1.9 was released, please bump package. Simply renaming ebuild seems to work. Reproducible: Always
Nikoli, ping :)
Yet another version has been released. The ebuild in the tree has remained unchanged for over half a year, although wt has already seen three updates. Is the ebuild still maintained?
It was maintained for eiskadcpp. Since upstream decided not to use wt, library became much less maintained. I guess it's much easier to drop it from the tree until somebody steps in and starts maintain it. Peter are you interested in this? If yes I can proxy commits for you.
If someone want to (proxy) maintain this package, please proceed, now I do not use wt anyhow. Upstream seems to break tests, src_test needs a lot fixing.
Peter any progress here? :) In case you stuck probably Nikoli may help.
Peter -- I have an interest in this package, and noticed that is currently masked pending removal (due to lack of maintainer?) -- if the upstream is somewhat helpful, I should be able to take the package over if you want....let me know.
I've moved package mask to ebuilds and performed a simple first test of 3.2.0 ebuild - will test over the next week (biggest concern is probably determining exact dependencies and/or resolving any issues with boost). Updated metadata with maintainer info. Will only be unmasking version 3.2 ebuild when it is ready, not earlier bumps, at least initially - so tentatively setting this bug to wontfix. Note that all current ebuilds were already masked in package mask before I did updates so masking ebuilds should have no impact. Aggressive users can experimentally unmask 3.2.0 ebuild by adding it to their package.keywords flag, e.g. "=net-libs/wt-3.2.0 **"
