A prerequisite for getting beagle into portage. When wv opens a file, it opens in read-write mode. This causes beagle to run around in loops (as beagle uses wv for word doc parsing, but wv causes a possible write event to appear, so beagle tries to index it again, ...) wv upstream are aware and have said that the next release (1.1.0?) will not include this bug (and infact it will not be using libole2 for parsing either) Here's an updated ebuild and patch. OK for me to commit this?
Created attachment 69910 [details] wv-1.0.3-r1.ebuild
Created attachment 69911 [details, diff] files/wv-1.0.3-libole2-readonly.patch
in cvs